582600 - input.stage and input cron job

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Dave Dash [:davedash, :dd] (assign all bugs to mbrandt)]

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.

Comment 1

[Aakash Desai [:aakashd]]

I'm setting this as blocking the go to live bug as well.

Comment 2

[Shyam Mani [:fox2mike]]

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.

Comment 3

[Shyam Mani [:fox2mike]]

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!

Comment 4

[Shyam Mani [:fox2mike]]

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.

Comment 5

[Shyam Mani [:fox2mike]]

Okay, seems like a cache issue. Cron will run on prod at 05 past midnight.

Calling this fixed.