TALES memcache should be shared between production appservers
Bug #539474 reported by
Stuart Bishop
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Medium
|
Stuart Bishop | ||
Bug Description
Currently, the TALES memcache extension uses the current LPCONFIG to form part of the key. This is to stop lpnet sharing cache with edge.
Unfortunately, this is too sensitive as each of our appservers has a unique LPCONFIG to allow each appserver to connect as a unique database user, unique OOPS prefix etc. So instead of just stopping edge & lpnet from sharing cache we stop all appservers from sharing cache. This defeats much of the gains from using memcache.
We need a replacement for LPCONFIG when forming the memcache key that allows lpnet appservers to share cache with other lpnet appservers but not with edge appservers.
| Changed in launchpad-foundations: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
Revision history for this message
| Gary Poster (gary) wrote | #1 |
| Changed in launchpad-foundations: | |
| assignee: | nobody → Stuart Bishop (stub) |
| status: | Triaged → Fix Committed |
| milestone: | none → 10.03 |
Revision history for this message
| Ursula Junque (ursinha) wrote Bug fixed by a commit | #2 |
| tags: | added: qa-needstesting |
Revision history for this message
| Ursula Junque (ursinha) wrote | #3 |
| tags: |
added: qa-ok removed: qa-needstesting |
| Changed in launchpad-foundations: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
As we discussed today, I'm fine with stripping out numerals from the LPCONFIG as a quick solution for now, while we are testing and learning.