Closed Bug 725781 Opened 14 years ago Closed 13 years ago

[basket] Celery servers for basket email service

Categories

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

Product:
Infrastructure & Operations Graveyard
Component:
WebOps: Other
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nmaul, Assigned: jd)

References

Details

Due to responsys timeout/failure problems, the basket service is able to process outgoing emails through Celery jobs, which allows them to happen out-of-band and be retry-able. We should get them access to something. basket.mozilla.com and .org are on the genericrhel6 cluster in PHX1. Do we have a Celery server/cluster for genericrhel6 apps to use? If not, let's create one.
See Also: → 705916
This is somewhat high priority, as we are switching to a new email provider and their API seems to be a good bit slower. Since it's blocking, the page takes a while to load.
Component: Server Operations → Server Operations: Web Operations
(In reply to Jake Maul [:jakem] from comment #0) > basket.mozilla.com and .org are on the genericrhel6 cluster in PHX1. Do we > have a Celery server/cluster for genericrhel6 apps to use? If not, let's > create one. We recently added celery nodes to get the generic cluster: https://mana.mozilla.org/wiki/display/websites/Generic+Cluster#GenericCluster-Hardware We will still need to configure a celery instace and rabbitmq queue specific to basket in puppet.
Assignee: server-ops → jcrowe
This is becoming a big problem for MDN (developer.mozilla.org). Bumping priority.
Severity: normal → critical
I set this up. There is a separate instance for each of dev, stage, and prod. The ./manage.py shell is not working which means I cannot run my normal tests for this, so... fingers crossed. Good Luck :)
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Summary: Celery servers for basket email service → [basket] Celery servers for basket email service
Wait, so the Celery servers are set up? How can we test them? The basket servers haven't been switched to use it yet, right? Just want to make sure we test it to make sure it's working correctly. I need to figure out the right way to fire off retries on error. I don't want it to get into an infinite loop if I mess something up in the basket code and it's trying to submit the wrong values to ExactTarget or something. I suppose it should only retry on connection failure.
Blocks: 730388
We can continue the discussion in the new bug I just cloned from this one.
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.