Closed Bug 1079518 Opened 5 years ago Closed 4 years ago

dzAlerts should stop requesting data from Datazilla after 10 HTTP 404 responses

Categories

(Datazilla Graveyard :: Metrics, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jgriffin, Unassigned)

References

Details

Currently, it doesn't abort a poll until 100 consecutive HTTP 404's, but this is overkill; it should stop after a single HTTP 404, and then resume polling after 60s.
Per Jeads:

"I think it would be better to reduce the number of contiguous 404 errors you're polling through. Try something like 10, that will reduce the chances of you getting blocked the next time we get scanned during dzAlert polling. We're using auto_increment on the objectstore (https://github.com/mozilla/datazilla/blob/master/datazilla/model/sql/template_schema/schema_objectstore.sql.tmpl#L16) so there won't be large id gaps. The only possibility that I know of for an id gap in that circumstance is the use of "ON DUPLICATE KEY UPDATE" on an auto_increment column and we have no unique keys to do that with on that table. "
Summary: dzAlerts should stop requesting data from Datazilla after a single HTTP 404 response → dzAlerts should stop requesting data from Datazilla after 10 HTTP 404 responses
Currently running every 10min, and stopping when 10 errors are encountered.  We will leave this bug open to observe the short term effects.
Blocks: 962378
dzAlerts is a dead project
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.