+++ This bug was initially created as a clone of Bug #1065152 +++ Similarly to bug 1064457, we need to switch celery from using vendor libraries to virtualenv. This was already done for sumo-dev, but as we roll out the branch that switches our dependency system from vendor to virtualenv on sumo-stage and sumo-prod, we need the celery scripts updated there. Also, there will need to be coordination between us all during the switch, so that we can ensure as little downtime on celery task processing as possible.
Summary: Switch celery scripts from using vendor for libraries to virtualenv → Switch celery stage/prod scripts from using vendor to virtualenv
as discussed on irc, the virtualenv celery configuration has now been pushed to stage.
as part of this activity, i noticed the dev and stage celery nodes were quite resource (memory) constrained. they have now been bumped up from 2Gb memory to 4 and 6 respectively. testing was completed in stage by :deanj, :mythmon and :r1cky and the go ahead was given in #sumodev to push this change to prod. that's now complete. marking as r/fixed \o/
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Everything looks good on prod. Thanks!
Status: RESOLVED → VERIFIED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.