Closed Bug 1255417 Opened 9 years ago Closed 9 years ago

[mozillians.org] Fix KEY_PREFIX in django cache settings

Categories

(Infrastructure & Operations Graveyard :: WebOps: Community Platform, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nemo-yiannis, Assigned: ericz)

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2689] )

While debugging an issue in mozillians-dev.allizom.org it turned out that there is a misconfiguration in mozillians CACHE settings. * We need to make sure that CACHE entry in mozillians/settings/local.py has KEY_PREFIX defined eg. * mozillians_dev_allizom_org * mozillians_allizom_org * mozillians_org For more information regarding the format see the example here [1]. * We need to remove the CACHE_MIDDLEWARE_KEY_PREFIX entry from the configuration since we are not using it and it's kind of misleading regarding the memcache prefix. Thank you! [1] https://pastebin.mozilla.org/8863089
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/2689]
That pastebin expired.
Assignee: server-ops-webops → eziegenhorn
So to be clear I'm changing the existing CACHE_MIDDLEWARE_KEY_PREFIX setting name to KEY_PREFIX for all mozillians environments. And the values should remain the same: 'mozillians_org' for prod, mozillians_allizom_org for stage and mozillians_dev_allizom_org for dev. Is that correct?
Sorry for the expired pastebin :\ Here is the example conf: CACHES = { 'default': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '<URIs>', 'KEY_PREFIX': '<KEY_PREFIX>' } } These are the changes we should do: * Configure the `KEY_PREFIX` entry on each env (dev/stage/prod) (it should be the same value with CACHE_MIDDLEWARE_KEY_PREFIX) * Remove the CACHE_MIDDLEWARE_KEY_PREFIX config entry
Also can we verify these on dev/stage first and then apply it on prod? It is not going to cause any downtime but let's make sure that these config changes work as expected.
dev and stage settings changed and deployed, please test.
Everything looks OK on dev/stage. Let's change the settings on prod.
Changed setting and deployed on prod as well.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.