Ticket #291 (new defect)

Opened 3 years ago

Last modified 3 years ago

FCGI instances are independent processes and do not share information

Reported by: obaltzer Assigned to: somebody
Priority: normal Milestone:
Component: Controller Version: HEAD
Severity: normal Keywords:
Cc:

Description

The problem with FCGI is that each ruby interpreter that is started is an independent instance and they do not share information. This causes problems with the selector cache, which when cleared in one instance it is not cleared in the other instances until it times out. The only approach I could think of right now is to have the cache running as a separate process to which instances connect via Unix socket, but this might be a little overkill.

Change History

01/05/06 12:24:13 AM changed by obaltzer

It might also be possible to make use of SQL views. In that case each selector is represented by an SQL view which is (hopefully) cached by the DBMS.