missing windows/nightly data
Categories
(Cloud Services :: Mission Control, defect)
Tracking
(Not tracked)
People
(Reporter: jcristau, Unassigned)
References
Details
https://missioncontrol.telemetry.mozilla.org/#/nightly/windows currently has content crashes but nothing else.
The dev instance at https://data-missioncontrol.dev.mozaws.net/#/nightly/windows does have data.
Comment 2•7 years ago
|
||
Checking new relic, I think database updates are timing out, seemingly in the phase when we're calculating rates.
Things to do:
- Set higher thresholds. Currently the soft timeout (which is really the limit for how long things can take despite its name) is set at 10 minutes.
- If we're failing here, it probably indicates that we have a db query that's not hitting an index and taking a long time. This might be hard to fix in a robust way, but maybe we could consider expiring old data (> 6 months). I'll investigate this.
Comment 3•7 years ago
|
||
I just noticed this is happening again with Win nightly, see https://missioncontrol.telemetry.mozilla.org/#/?channel=nightly. We can use the dev instance for channel tomorrow if need be.
Comment 4•7 years ago
|
||
(In reply to Marcia Knous [:marcia - needinfo? me] from comment #3)
I just noticed this is happening again with Win nightly, see https://missioncontrol.telemetry.mozilla.org/#/?channel=nightly. We can use the dev instance for channel tomorrow if need be.
Yeah, sorry, I've been working on this the whole time and found a big pile of other issues with mission control which needed to be fixed. The dev instance should be more reliable for now (I expired a bunch of older data on it, so there should be few if any timeouts there).
Comment 5•7 years ago
|
||
https://github.com/mozilla/missioncontrol/commit/95b2cf473361b0ffecc74f5be59df34cd770d6d5 should fix this when it's applied to production (I'll do a deploy tomorrow, after we've verified bug 1542820 is fixed).
Comment 6•7 years ago
|
||
(In reply to William Lachance (:wlach) (use needinfo!) from comment #5)
https://github.com/mozilla/missioncontrol/commit/95b2cf473361b0ffecc74f5be59df34cd770d6d5 should fix this when it's applied to production (I'll do a deploy tomorrow, after we've verified bug 1542820 is fixed).
Filed bug 1543541 to get this deployed.
Comment 7•7 years ago
•
|
||
Looks like we might need some manual expiry to get things working again. Bug 1544444
Updated•7 years ago
|
Comment 9•7 years ago
|
||
This is still not completely fixed -- things still appear to be timing out when doing summary calculations even with the data expiry. Filed bug 1544801 to deploy a release with increased timeouts, which will hopefully help.
Comment 10•6 years ago
|
||
I think the 1.10 update should finally fix this, once deployed.
Reporter | ||
Comment 11•5 years ago
|
||
I guess we can close this?
Description
•