Closed
Bug 1164514
Opened 10 years ago
Closed 10 years ago
SUMO -dev, -stage, prod: Please update CACHES['default']['backend'] setting.
Categories
(Infrastructure & Operations Graveyard :: WebOps: Community Platform, task)
Infrastructure & Operations Graveyard
WebOps: Community Platform
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rrosario, Assigned: cliang)
References
Details
(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/1151] )
We the setting currently looks something like:
CACHES = {'default': {'BACKEND': 'caching.backends.memcached.CacheClass',...
Please change the BACKEND value to the one here:
CACHES = {'default': {'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',...
The rest can remain the same.
Please do -dev and -stage together first. Then we can make sure nothing is on fire and move on to prod. Thanks!
| Assignee | ||
Updated•10 years ago
|
Assignee: server-ops-webops → cliang
| Assignee | ||
Comment 1•10 years ago
|
||
Change pushed out to -dev and -stage; Apache has been gracefully restarted in both environments. Let me know if there are additional pieces that need to be rebooted and/or if everything looks good to you.
Comment 2•10 years ago
|
||
I poked at some cache-using parts of the site, and everything appears to be working. I don't see anything on fire in Errormill, so I say lets move forward and apply this change on -prod.
| Assignee | ||
Comment 3•10 years ago
|
||
Change pushed out to -prod; Apache has been gracefully restarted on the SUMO prod web-heads. Let me know if there are additional pieces that need to be rebooted and/or if everything looks good to you.
Comment 4•10 years ago
|
||
Prod looks good. I don't think there is any thing else that we need here, thank you!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
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
•