civetweb health check

civetweb health check

[Srikanth Madugundi]

Hi,

We are planning to move our radosgw setup from apache to civetweb. We
were successfully able to setup and run civetweb on a test cluster.

The radosgw instances are fronted by a VIP with currently checks the
health by getting /status.html file, after moving to civetweb the vip
is unable to get the health of radosgw server using /status.html
endpoint and assumes the server is down.

I looked at ceph radosgw documentation and did not find any
configuration to rewrite urls. What is the best approach for VIP to
get the health of radosgw?

Thanks
Srikanth

Re: civetweb health check

[Wido den Hollander]

On 05-08-15 18:37, Srikanth Madugundi wrote:
> Hi,
> 
> We are planning to move our radosgw setup from apache to civetweb. We
> were successfully able to setup and run civetweb on a test cluster.
> 
> The radosgw instances are fronted by a VIP with currently checks the
> health by getting /status.html file, after moving to civetweb the vip
> is unable to get the health of radosgw server using /status.html
> endpoint and assumes the server is down.
> 
> I looked at ceph radosgw documentation and did not find any
> configuration to rewrite urls. What is the best approach for VIP to
> get the health of radosgw?
> 

You can simply query /

This is what I use in Varnish to do a health check:

backend rgw {
    .host               = "127.0.0.1";
    .port               = "7480";
    .connect_timeout    = 1s;
    .probe = {
        .timeout   = 30s;
        .interval  = 3s;
        .window    = 10;
        .threshold = 3;
        .request =
            "GET / HTTP/1.1"
            "Host: localhost"
            "User-Agent: Varnish-health-check"
            "Connection: close";
    }
}

Works fine, RGW will respond with a 200 OK in /

Wido

> Thanks
> Srikanth
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: civetweb health check

[Srikanth Madugundi]

hitting '/' endpoint worked.

Thanks
Srikanth

On Thu, Aug 6, 2015 at 1:26 AM, Wido den Hollander <wido@42on.com> wrote:
>
>
> On 05-08-15 18:37, Srikanth Madugundi wrote:
>> Hi,
>>
>> We are planning to move our radosgw setup from apache to civetweb. We
>> were successfully able to setup and run civetweb on a test cluster.
>>
>> The radosgw instances are fronted by a VIP with currently checks the
>> health by getting /status.html file, after moving to civetweb the vip
>> is unable to get the health of radosgw server using /status.html
>> endpoint and assumes the server is down.
>>
>> I looked at ceph radosgw documentation and did not find any
>> configuration to rewrite urls. What is the best approach for VIP to
>> get the health of radosgw?
>>
>
> You can simply query /
>
> This is what I use in Varnish to do a health check:
>
> backend rgw {
>     .host               = "127.0.0.1";
>     .port               = "7480";
>     .connect_timeout    = 1s;
>     .probe = {
>         .timeout   = 30s;
>         .interval  = 3s;
>         .window    = 10;
>         .threshold = 3;
>         .request =
>             "GET / HTTP/1.1"
>             "Host: localhost"
>             "User-Agent: Varnish-health-check"
>             "Connection: close";
>     }
> }
>
> Works fine, RGW will respond with a 200 OK in /
>
> Wido
>
>> Thanks
>> Srikanth
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>