For staging (and after the push, production) Crontab needs setting up for running ./manage.py cron cluster at around midnight. It only needs to run on an admin node, and is memory and cpu intensive. In the future we can supply crontabs.
7 years ago
I'm setting this as blocking the go to live bug as well.
We ran into some issues working on this yesterday, so I'll work with Dave today before the push to get this going on stage.
Seems like this is good. [root@mrapp-stage02 reporter]# /data/virtualenvs/input/bin/python26 /data/www/input.stage.mozilla.com/reporter/manage.py cron cluster Beginning clustering Clustering happy... Clustering happy, 4.0b1 Clustering sad... Clustering sad, 4.0b1 Leaving bug open for production. Thanks Dave!
Ran on Prod, by hand : [root@mradm02 vendor]# /usr/bin/python26 /data/generic/www/django/input.mozilla.com/reporter/manage.py cron cluster Beginning clustering Clustering happy... Clustering happy, 4.0b1 Clustering sad... Clustering sad, 4.0b1 Don't see clusters on prod though.
Okay, seems like a cache issue. Cron will run on prod at 05 past midnight. Calling this fixed.