Closed Bug 1144476 Opened 9 years ago Closed 9 years ago

[heartbeat] stop logging updated_ts errors

Categories

(Input Graveyard :: Backend, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: lgp171188, Mentored)

Details

(Whiteboard: u=gregg c=heartbeat p= s=input.2015q1)

Right now if we get an HB packet where the updated_ts is <= the one in the db, we log an error.

https://github.com/mozilla/fjord/blob/dad6bea148fa681a29e0848fa32ec6729da25429/fjord/heartbeat/api_views.py#L78

We know a lot about this error now. It's coming predominantly because the client fires off two HTTP POSTS one right after the other. Seems like it's not uncommon for the second to get handled before the first.

Given that, we stop recording the error. Just return an HTTP 400 to the client and move along.
I think the way I want to fix this is to change rest_error() to have an argument specifying whether to log the error or not--have it default to logging the error.

Then change this use of rest_error() to tell rest_error() to not log the error.
Passing this to LGuruprasad who just did it.

PR: https://github.com/mozilla/fjord/pull/526

Landed in master: https://github.com/mozilla/fjord/commit/026d9ae21d42d906231090c807771e8a0202097e

Will push out on next deploy.
Assignee: nobody → lgp171188
Mentor: willkg
Status: NEW → ASSIGNED
Pushed to prod just now.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.