Topic on User talk:Magnus Manske

Current the number of attempts after hitting maxlag in QuickStatements is 3 . After phab:T221774 maxlag takes the query service lag into account, and it is updated every minute. This means once query service is lagged we need at least one minute to get it refreshed. Sometimes it takes up to one hour to make maxlag return to normal (which needs 720 retries when one retry takes five second). See for a live example affected by this. Therefore the number of attempts is too low and should be increased to (preferred) 1000.

@Ayack, Bargioni, SCIdude: and other users running QuickStatements batch after 15:36 UTC: you may need to reset errors of batchs, probably multiple times, for this reason.

I still get 7% errors (yesterday), Is this the same issue?

Bump up as it's still a issue which affects nearly all backend batches but a fix is somewhat trivial.

Well, that code change applies only to in-browser runs; batches use https://github.com/magnusmanske/quickstatements_rs

Trying to adapt that now.

I have changed the rust-based part (batches) to use more repeats.

I also updated the PHP code accordingly.