Opened 2 years ago
Last modified 13 months ago
#2834 new Defect
Memcache namespace conflict
| Reported by: | coldtrick | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Long Term Future Release |
| Component: | Core | Version: | 1.8 |
| Severity: | minor | Keywords: | memcache, conflict, namespace |
| Cc: | brett@… | Difficulty: | easy |
Description
First of, I know Memcache support is experimental! ;)
When you have 2 Elgg installations (production, development) on one memcache server you run into a problem, because they both use the same namespace ('default').
To prevent this it would be nice to be able to configure a namespace prefix/postfix in settings.php (where you configure the memcache servers)
Change History (4)
comment:1 Changed 2 years ago by cash
- Difficulty set to easy
- Milestone changed from Needs Review to Elgg 1.7.8
comment:2 Changed 2 years ago by cash
- Milestone changed from Elgg 1.7.8 to Future Release
comment:3 Changed 19 months ago by janlb
A workaround: run two separate memcache instances on your server (different ports?)
comment:4 Changed 13 months ago by coldtrick
- Version changed from 1.7 to 1.8
patch supplied in https://github.com/Elgg/Elgg/pull/191
Note: See
TracTickets for help on using
tickets.

Interested in submitting a patch?