Task #4855
Investigate APC slam problem
| Status: | Closed | Start date: | 2009-10-02 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 0% |
|
| Category: | Cache | |||
| Target version: | - | |||
| Sprint: | Has patch: | |||
| PHP Version: | Complexity: |
Description
See http://t3.dotgnu.info/blog/php/user-cache-timebomb for the problem and http://pecl.php.net/bugs/bug.php?id=16814 as well as http://pecl.php.net/bugs/bug.php?id=16843 for the "PHP solution".
Do we need to consider the basic problem and change the way cache entries expire? Or is this solved by our site lock anyway (if it is enabled again)?
Related issues
Associated revisions
[~TASK] FLOW3 (Cache): Fixed a failing APC backend test
One test was failing, probably due to an old APC version used (see #9538).
After upgrading to a more recent version of APC (3.1.5-dev) this other
tests failed due to the cache slam prevention mechanism.
Since that cannot be disabled (currently) via ini_set(), these tests
are now skipped if apc.slam_defense is set to 1.
Relates to: #4855
Resolves: #9538
Change-Id: I82577d149aebb608b4cb14d7cdb76422ce41d09a
History
#1 Updated by Karsten Dambekalns about 4 years ago
- Status changed from New to Closed
- Assigned To set to Karsten Dambekalns
If it ever comes up again, we'll deal with it.