Page MenuHomePhabricator

WDQS updater should have a keep running after error mode
Closed, DeclinedPublic

Description

The WDQS Updater fails if it sees more than 6 (?) errors in a row. Please make that parameter configurable, e.g. "Number of failures before quiting", and it should allow -1 or infinite, so that it keeps trying until success. The delay between retries should be progressive, e.g. 0s, 10s, 30s, 1m, 10min (max, don't raise above this).

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript

Right now it's hardcoded in RdfRepository class:

private int maxRetries = 6;
private int delay = 1000;

Probably not very hard to make configurable. Note this is for communication with Blazegraph, for Wikibase it's in WikibaseRepository class.

Smalyshev lowered the priority of this task from Medium to Low.Dec 13 2018, 6:22 PM
Gehel subscribed.

We're moving to a new streaming updater, so it does not make sense to keep investing in the old one. Let's close this.