Change Details

**Problem:** The lag of the query service is taken into account for throttling bots via maxlag. The current factor is 60. We want to increase it to 180 to be more realistic and not be too strict. This corresponds to an acceptable average lag between an edit being made and it showing up in the query service of 15 minutes. **Acceptance criteria:** [ ] acceptable maxlag is increased for the lag between an edit being made and it being reflected in the query service **Notes:** * We will try this and see if further adjustments are needed.

**Problem:** The lag of the query service is taken into account for throttling bots making edits to Wikidata using maxlag API parameter (i.e. the bot request "I want to make this edit and make request it to actually be made only if the current DB replication lag is not higher than X"). The current factor is 60. We want to increase it to 180 to be more realistic and not be too strict. This corresponds to an acceptable average lag between an edit being made and it showing up in the query service of 15 minutes (currently being 5 minutes). The expected impact/result here is the increased number of edits that are successfully made (i.e. replication lag is low enough for those to be saved), and the level of the lag between edits to DB and Query Service updates is acceptable for Query Service users. There is a configuration setting relevant for the said factory that would require to be changed. **Acceptance criteria:** [ ] acceptable maxlag is increased for the lag between an edit being made and it being reflected in the query service **Notes:** * We will try this and see if further adjustments are needed.

**Problem:** The lag of the query service is taken into account for throttling bots viamaking edits to Wikidata using maxlag API parameter (i.e. the bot request "I want to make this edit and make request it to actually be made only if the current DB replication lag is not higher than X"). The current factor is 60. We want to increase it to 180 to be more realistic and not be too strict. This corresponds to an acceptable average lag between an edit being made and it showing up in the query service of 15 minutes (currently being 5 minutes). The expected impact/result here is the increased number of edits that are successfully made (i.e. replication lag is low enough for those to be saved), This corresponds to an acceptable average lag between an edit being made and it showing up in the query service of 15 minutesand the level of the lag between edits to DB and Query Service updates is acceptable for Query Service users. There is a configuration setting relevant for the said factory that would require to be changed. **Acceptance criteria:** [ ] acceptable maxlag is increased for the lag between an edit being made and it being reflected in the query service **Notes:** * We will try this and see if further adjustments are needed.