Opened 16 years ago
Closed 15 years ago
#12484 closed (wontfix)
Document that cmemcache is definetly not thread safe
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.1 |
| Severity: | Keywords: | cmemcache | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Using the cmemcache in threaded environment will eventually lead to cache failure.
[FATAL@1262456081.210803] mcm_get_line():1547: memcache(4) protocol error: no \r before \n [FATAL@1262456081.282046] mcm_get_line():1547: memcache(4) protocol error: no \r before \n [FATAL@1262456081.282084] mcm_fetch_cmd():1159: memcache(4) protocol error: protocol, expected a response [FATAL@1262456081.761118] mcm_get_line():1547: memcache(4) protocol error: no \r before \n
Steps to reproduce:
- /usr/sbin/ab -n 100 -c 2 http://example.com/my_cached_page
Maybe the solution is to use threading.local to store cmemcache objects.
Change History (3)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
| Component: | Cache system → Documentation |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:3 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Since support for cmemcache was deprecated in 1.2 due to a lack of maintenance on the cmemcache library itself, probably not worth fixing.