You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by Dmitriy Shirchenko <ca...@gmail.com> on 2015/11/09 20:45:40 UTC
Health checks for non-HTTP protocols
Hi everyone!
As we are trying to adopt Aurora, one of the things we need is support for
health checking applications interacting via non-HTTP protocols.
Has this been brought up before or can someone please give us guidance on
how to make this work?
Thanks for your help,
Dmitriy!
Re: Health checks for non-HTTP protocols
Posted by Bill Farner <wf...@apache.org>.
The upside to what Ben described above is that you can then still handle
the graceful teardown in the way that best suits your application.
On Mon, Nov 9, 2015 at 12:40 PM, benley@gmail.com <be...@gmail.com> wrote:
> A common pattern I've seen has been to add a trivial http listener to your
> apps that responds to the /health endpoint, and have Aurora check that port
> rather than the non-http protocol port(s). For third-party code where it's
> not practical to do that, one might add a secondary process in the same
> task that performs protocol-specific health checking of your app, and
> reports the result on its own /health http listener.
>
> On Mon, Nov 9, 2015 at 12:29 PM Dmitriy Shirchenko <ca...@gmail.com>
> wrote:
>
> > Hi everyone!
> >
> > As we are trying to adopt Aurora, one of the things we need is support
> for
> > health checking applications interacting via non-HTTP protocols.
> >
> > Has this been brought up before or can someone please give us guidance on
> > how to make this work?
> >
> > Thanks for your help,
> > Dmitriy!
> >
>
Re: Health checks for non-HTTP protocols
Posted by "benley@gmail.com" <be...@gmail.com>.
A common pattern I've seen has been to add a trivial http listener to your
apps that responds to the /health endpoint, and have Aurora check that port
rather than the non-http protocol port(s). For third-party code where it's
not practical to do that, one might add a secondary process in the same
task that performs protocol-specific health checking of your app, and
reports the result on its own /health http listener.
On Mon, Nov 9, 2015 at 12:29 PM Dmitriy Shirchenko <ca...@gmail.com>
wrote:
> Hi everyone!
>
> As we are trying to adopt Aurora, one of the things we need is support for
> health checking applications interacting via non-HTTP protocols.
>
> Has this been brought up before or can someone please give us guidance on
> how to make this work?
>
> Thanks for your help,
> Dmitriy!
>
Re: Health checks for non-HTTP protocols
Posted by Dmitriy Shirchenko <ca...@gmail.com>.
Thanks for your responses!
Is there any philosophical opposition to adding support for arbitrary
health check shell out commands to be run as part of health checking? Ie
allowing someone to specify a command line out instead of an HTTP endpoint?
If not, then I would love to take a crack and submit a patch with that.
And great points about graceful shutdown. I guess in the future support for
that would need to get added as well since those require HTTP.
Thanks!
On Mon, Nov 9, 2015 at 11:45 AM, Dmitriy Shirchenko <ca...@gmail.com>
wrote:
> Hi everyone!
>
> As we are trying to adopt Aurora, one of the things we need is support for
> health checking applications interacting via non-HTTP protocols.
>
> Has this been brought up before or can someone please give us guidance on
> how to make this work?
>
> Thanks for your help,
> Dmitriy!
>