Anonymous | Login | Signup for a new account | 2024-03-29 00:57 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Relationship Graph | [ View Issue ] [ Dependency Graph ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0001231 | [In-Portal CMS] Caching System | bug report | always | 2012-03-24 15:38 | 2012-07-25 05:31 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0001231: Bug in parallel cache rebuild protection | ||||
Description |
We've implemented parallel cache rebuild protection in 5.2.0-B1 by setting lock before creating new cache. This ensured that all other requests were receiving old cache version or just waiting for a lock to be released. However I've found a bug in that system too, when multiple visitors, who encountered a missing/outdated cache would set lock in parallel and start rebuild process. This of course would be slightly smaller number of parallel rebuild requests then without protection added in 5.2.0-B1, but still needs to be fixed. |
||||
Additional Information |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |