Closed Bug 1542852 Opened 6 years ago Closed 6 years ago

implement safeguards on pulse.m.o to mitigate the probability of future pulse outages

Categories

(Webtools :: Pulse, defect)

Product:
Webtools
Component:
Pulse
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kmoir, Unassigned)

References

Details

User Story

Proper guardrails in place for folks who are testing code against production pulse or recommendation not to test against production pulse

Investigate and implement as reasonable

Implement quotas for the number of queues ppl can create?
Implement quotas for the number of messages in a queue?
What are the defaults for new queues with respect to the number of messages in the queue? Are they reasonable or should they be adjusted?

Blocks: 1542805
Summary: impelmenent safeguards on pulse.m.o to mitigate the probability of future pulse outages → implement safeguards on pulse.m.o to mitigate the probability of future pulse outages
User Story: (updated)

This is exactly what PulseGuardian does :)

Note that we could also use a policy on max queue length:
https://github.com/mozilla-services/pulseguardian/pull/168

but given that pulse has been working fine for years until pulseguardian went down (bug 1540758), I don't think we need to get too creative here.

closing, see comments 1 and 2.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.