Closed Bug 749346 Opened 12 years ago Closed 12 years ago

Figure out how to split crons between datacenter pods

Categories

(addons.mozilla.org Graveyard :: Code Quality, defect)

Product:
addons.mozilla.org Graveyard
Component:
Code Quality
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: clouserw, Unassigned)

References

Details

We're going to have multiple data centers as well as investigate "pods" which can house AMO close to end users.  When we deploy these pods we don't want the crons running in each one.  I suspect we'll have crons running in one place (a datacenter) and anything that needs to run close to the end user running in each pod.

This bug is to determine:

1) if anything falls in the second category

2) how do we differentiate the two and have things run in the correct spot?

pods will have their own configs so this will probably be something in settings_local
I didn't see anything that needed to run in each pod.  Maybe a cleanup script to delete temporary files once in a while.  Otherwise we're good just having stuff running in the main DC.
closing based on comment 1.  With the change to services infra, this will probably change anyway.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.