Increase percentage of crashes that are sent to stage collectors

RESOLVED FIXED

Status

Socorro
General
RESOLVED FIXED
2 years ago
2 years ago

People

(Reporter: mbrandt, Assigned: jp)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [fromAutomation])

(Reporter)

Description

2 years ago
I'd like to up the percentage of crashes being sent from prod to stage and it's collectors to get a more representative collection of data.

On production's collector boxes, let's raise crashmover's destination.storage3.throttle from 10 to 20 to send more data to the stage collectors.
(Reporter)

Updated

2 years ago
Flags: needinfo?(jschneider)
(Reporter)

Updated

2 years ago
Summary: [prod] Increase percentage of crashes that are sent to stage's → [prod] Increase percentage of crashes that are sent to stage collectors
Whiteboard: [fromAutomation]
I agree. I think we should definitely bump it from 10 to 20.
Assignee: nobody → jschneider
Flags: needinfo?(jschneider)
Summary: [prod] Increase percentage of crashes that are sent to stage collectors → Increase percentage of crashes that are sent to stage collectors
(Reporter)

Updated

2 years ago
Blocks: 1213247
(Reporter)

Updated

2 years ago
Blocks: 1213200
:jp the idea is to change the crashmover config to flow more crashes into the RMQ stage submmission queue:

existing:
    destination.storage3.throttle=10

what we need:
    destination.storage3.throttle=20

that ought to double the number of crashes flowing into staging.
(Assignee)

Comment 3

2 years ago
Great, thanks lars!

I've run it and set us to 20%...:mbrandt is that sufficient?
Flags: needinfo?(mbrandt)
(Reporter)

Comment 4

2 years ago
Thanks JP! Much appreciated. Let's call this good for now. I think time will tell if this was the right tweak. I'll file a bug if we need more.
Flags: needinfo?(mbrandt)
Resolve?
JP, last time I ssh'ed into one of the stage processors I noticed it hovered around a load of 10. Should we upgrade them to xlarge2 (or whatever it was prod uses?)
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.