From: Wido den Hollander <wido@42on.com>
To: Srikanth Madugundi <srikanth.madugundi@gmail.com>,
ceph-devel@vger.kernel.org
Subject: Re: civetweb health check
Date: Thu, 06 Aug 2015 10:26:31 +0200 [thread overview]
Message-ID: <55C31A37.9050302@42on.com> (raw)
In-Reply-To: <CACAg-u9r6jXW7C5dWes3_AnkGkXvzS_vhmw044i4n0mAc31oUw@mail.gmail.com>
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
>
next prev parent reply other threads:[~2015-08-06 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 16:37 civetweb health check Srikanth Madugundi
2015-08-06 8:26 ` Wido den Hollander [this message]
2015-08-07 4:34 ` Srikanth Madugundi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C31A37.9050302@42on.com \
--to=wido@42on.com \
--cc=ceph-devel@vger.kernel.org \
--cc=srikanth.madugundi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.