Feature #36


fcgi remote backends intelligent availability check

Added by glen almost 19 years ago. Updated over 7 years ago.

Target version:


say, i have configured three fcgi-handlers for one URI in lighttpd.
if lighttpd, sees that fcgi backend is unavailable (say, connection refused), it marks it offline (fcgi server disabled). if in case all of them are disabled, it would be neccessary that the fcgi servers are instantly checked for availability again, without the existing timeout. since the servers might have returned. real case: i restarted fcgi backend daemons one by one. and i had to restart lighttpd to make it again serve fcgi requests.

my idea would be that the timeout for checking fcgi backend is lowered for fcgi server, if all of them are unavailable for same URI, and perhaps exponentally increased if the check of all fcgi servers fails (again). and of course initial first check must be done instantly (ie without timeout). and perhaps if the fcgi server becames available, the disabled-timeout is set back to default normal value.

Actions #1

Updated by jan over 18 years ago

  • Status changed from New to Assigned
Actions #2

Updated by Anonymous over 18 years ago

Please also make #define FCGI_RETRY_TIMEOUT (5 * 60) configurable at least at global level. A short restart of manually spawned PHP processes after php.ini corrections leads to excessive vhost unavailability.

-- arkadi

Actions #3

Updated by jan over 18 years ago

FCGI_RETRY_TIMEOUT is already gone in svn.

Actions #4

Updated by Anonymous almost 18 years ago

until this above is not implemented, what about improving retry_timeout checks.

when one of the fcgi servers is out (connection refused). then webserver cycles such log entries every $FCGI_RETRY_TIMEOUT seconds:

2005-12-05 20:27:28: (mod_fastcgi.c.2493) fcgi-server re-enabled: 3001
2005-12-05 20:27:29: (mod_fastcgi.c.2665) establishing connection failed: Connection refused
2005-12-05 20:27:29: (mod_fastcgi.c.2804) fcgi-server disabled: 3001
i propose to check the fcgi-server:
  1. in tcp level (establish tcp connection).
  2. fcgi protocol level.

and if those succeed, mark fcgi-server online, and send next request there.

i'm not sure, but i think it's possible to do fcgi service check without actually doing FCGI_BEGIN_REQUEST. because sending actual request to fcgi-server to test if it's alive is not very safe operation.

-- glen

Actions #5

Updated by mike503 over 16 years ago

whatever the intelligent solution is here please make sure it's implemented into the mod_proxy_core replacement for fcgi in 1.5 :) thanks.

Actions #6

Updated by stbuehler about 15 years ago

  • Target version changed from 1.4.20 to 1.4.21
Actions #7

Updated by icy almost 15 years ago

  • Target version changed from 1.4.21 to 1.4.22
  • Pending set to No
  • Patch available set to No
Actions #8

Updated by stbuehler almost 15 years ago

  • Target version changed from 1.4.22 to 1.4.23
Actions #9

Updated by stbuehler over 14 years ago

  • Target version changed from 1.4.23 to 1.4.x
Actions #10

Updated by gstrauss over 7 years ago

  • Status changed from Assigned to Fixed
  • % Done changed from 0 to 100
Actions #11

Updated by stbuehler over 7 years ago

  • Assignee deleted (jan)
Actions #12

Updated by stbuehler over 7 years ago

  • Target version changed from 1.4.x to 1.4.40

Also available in: Atom