Closed
Bug 740396
Opened 14 years ago
Closed 14 years ago
[SUMO Prod] Update CACHES setting in settings_local.py
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rrosario, Assigned: jason)
Details
Please update our cache settings by removing the current CACHE_BACKEND setting and adding the following (updating the hosts with the right values).
CACHES = {
'default': {
'BACKEND': 'caching.backends.memcached.CacheClass',
'LOCATION': ['host1:11211', 'host2:11211'],
'KEY_PREFIX': 'sumo-20120329:',
'TIMEOUT': 600,
}
}
Once this is in place, we need to deploy with chief so don't touch the wsgi files, restart apache, or anything like that.
| Assignee | ||
Updated•14 years ago
|
Assignee: server-ops → jthomas
| Assignee | ||
Comment 1•14 years ago
|
||
Done.
# Cache Settings
-CACHE_BACKEND = 'caching.backends.memcached://memcache-sumo01:11211;memcache-sumo02:11211'
-CACHE_PREFIX = 'sumo_kitsune:'
-
+CACHES = {
+ 'default': {
+ 'BACKEND': 'caching.backends.memcached.CacheClass',
+ 'LOCATION': ['memcache-sumo01:11211', 'memcache-sumo02:11211'],
+ 'KEY_PREFIX': 'sumo-20120329:',
+ 'TIMEOUT': 600,
+ }
+}
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•7 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•