Closed Bug 1128135 Opened 10 years ago Closed 10 years ago

Nightly from 2015-01-23 caused +20% increase in Telemetry upload failures

Categories

(Toolkit :: Telemetry, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla38
Tracking Status
firefox36 --- unaffected
firefox37 --- fixed
firefox38 --- fixed

People

(Reporter: vladan, Assigned: gfritzsche)

References

Details

Attachments

(1 file)

For some reason, Nightly has started to get errors while trying to send its Telemetry pings to the Telemetry server, starting with the Nightly from January 23rd. The server's submission count graph shows it as well: http://ec2-50-112-66-71.us-west-2.compute.amazonaws.com:4352/#sandboxes/TelemetryChannelMetrics60DaysAggregator/outputs/TelemetryChannelMetrics60DaysAggregator.nightly.cbuf We also need to report the HTTP error code in TelemetryLog when the submission fails.
- It does look like it's related to e10s.. E10S_AUTOSTART ratio went down with the Nightly from January 23rd: http://mzl.la/1Kfv96S - The fix for missing clientIDs (bug 1119281) is the only TelemetryPing.jsm modification close to Jan 23rd
Blocks: 1069869
Summary: Nightly from 2015-01-23 caused Telemetry upload failures → Nightly from 2015-01-23 caused +20% increase in Telemetry upload failures
(In reply to Vladan Djeric (:vladan) from comment #2) > - It does look like it's related to e10s.. E10S_AUTOSTART ratio went down > with the Nightly from January 23rd: http://mzl.la/1Kfv96S Hm, did it go down in volume relative to other measurements? > - The fix for missing clientIDs (bug 1119281) is the only TelemetryPing.jsm > modification close to Jan 23rd Hm, i see a potential shutdown issue there - a missing return here: https://hg.mozilla.org/mozilla-central/rev/df2f2df820a8#l1.60 Sad that this slipped through :( I'm not sure if that would account for the dip though.
(In reply to Georg Fritzsche [:gfritzsche] from comment #4) > > - The fix for missing clientIDs (bug 1119281) is the only TelemetryPing.jsm > > modification close to Jan 23rd > > Hm, i see a potential shutdown issue there - a missing return here: > https://hg.mozilla.org/mozilla-central/rev/df2f2df820a8#l1.60 If that is the issue, we should have recovered on Jan 29 or 30, as bug 1123384 didn't port this as i landed it and we have a return for the AsyncShutdown blocker again: https://hg.mozilla.org/mozilla-central/annotate/5cbae82bdb4b/toolkit/components/telemetry/TelemetrySession.jsm#l957
Nightly submission count increased with Jan 29th build: http://mzl.la/16bSPvA TELEMETRY_SUCCESS rate went back up to 95% with Jan 29th build: http://mzl.la/1vpvOl2 let's keep an eye on the rates for a couple more days and then we can close this bug
Bug 1119281 was uplifted to Aurora, so we still need to fix this there.
Attachment #8558445 - Flags: review?(vdjeric)
Attachment #8558445 - Flags: review?(vdjeric) → review+
Comment on attachment 8558445 [details] [diff] [review] Aurora fix for not blocking on promise in TelemetryPing shutdown. Approval Request Comment [Feature/regressing bug #]: Bug 1119281 regression. [User impact if declined]: Missing shutdown synchronization and Telemetry submission failures. [Describe test coverage new/current, TreeHerder]: Obvious fix that restores previous behaviour. [Risks and why]: Low-risk; obvious fix restoring previous behavior. [String/UUID change made/needed]: None.
Attachment #8558445 - Flags: approval-mozilla-aurora?
Comment on attachment 8558445 [details] [diff] [review] Aurora fix for not blocking on promise in TelemetryPing shutdown. Simple fix for Telemetry. Aurora+
Attachment #8558445 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
https://hg.mozilla.org/releases/mozilla-aurora/rev/f1c0a517ebc7 Given that bug 1119281 already needs rebasing for Fx36 uplift anyway, I assume that this fix will be rolled into that patch.
Assignee: nobody → gfritzsche
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #11) > Given that bug 1119281 already needs rebasing for Fx36 uplift anyway, I > assume that this fix will be rolled into that patch. Yes, thank you.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: