Please may the wgsi config for treestatus dev/staging/prod be updated to add a new memcached.prefix key, with a unique value for each, eg "treestatus-dev", "treestatus-stage", "treestatus-prod", along the lines of the changes to the checked-in example config: https://github.com/mozilla/treestatus/compare/0c429f093afa9a591c3f0ab0b791582abfd748b5...090c76ebd68dad1cd8a3b2ed0f743b7f93a38568#L0R16 After that, please can treestatus master head be pushed to staging (https://github.com/mozilla/treestatus/commit/090c76ebd68dad1cd8a3b2ed0f743b7f93a38568), ready for confirmation & then prod push. Changelog: https://github.com/mozilla/treestatus/compare/0c429f093afa9a591c3f0ab0b791582abfd748b5...090c76ebd68dad1cd8a3b2ed0f743b7f93a38568#files_bucket Thank you :-)
grabbing this bug since i have context.
Assignee: server-ops-webops → cturra
dev has been sorted and i have now pushed this change, plus the memcache config change, to stage. :edmorley - can you please give it a test to confirm everything is functioning as expected before i push this to prod?
I'm getting the odd ISE 500 error - do we need to restart any services for the memcached change to take effect? (just to confirm - the prefix for stage has been set to something like 'treestatus-stage', right? :-))
(In reply to Ed Morley [:edmorley UTC+1] from comment #3) > I'm getting the odd ISE 500 error - do we need to restart any services for > the memcached change to take effect? since this is a new index, it shouldn't require a restart of our memcache nodes. > (just to confirm - the prefix for stage > has been set to something like 'treestatus-stage', right? :-)) correct. [firstname.lastname@example.org treestatus.allizom.org]# grep -i prefix tree-status/treestatus.wsgi 'memcached.prefix': 'treestatus-stage', i just had a look in the apache error logs and do not see anything out of the ordinary in there.
Seems fine again now - think we're just going to have to go for it (seeming unrelated to the changes landed).
Thank you for double checking though! :-)
production is now up to date, including the memcache prefix :)
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Thank you :-)
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.