codesite-noreply at google
Sep 1, 2009, 6:57 AM
Post #1 of 1
(181 views)
Permalink
|
|
Issue 555 in cherokee: Reverse Proxy fail over and backend detection
|
|
Status: New
Owner: ----
New issue 555 by plundis [at] areaindex: Reverse Proxy fail over and backend
detection
http://code.google.com/p/cherokee/issues/detail?id=555
Spoke with Alvaro about this---
Details:
Currently if you have servers behind Cherokee and a server becomes slow to
respond (accepts network connections but never delivers page) Cherokee will
hold opened until you set connection timeout. In our instance 2 minutes.
The user receives nothing just a blank page sitting there. Resources are
utilized keeping this dead space open.
Meanwhile ideally, you have other backend servers that Cherokee could send
the page to for processing that would work.
Since Cherokee doesn't currently detect this type of failure, other
requests will similarly end up on a failed backend like this that still has
network connectivity functioning.
Feature Request:
Provide for a user defined slow backend setting (i.e. if backend server
fails to respond with data or complete page in user defined time of 3
seconds then the backend is failing) - thus remove that backend from the
available pool Cherokee has for some defined time.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev [at] lists
http://lists.octality.com/listinfo/cherokee-dev
|
