| Lucas_Werkmeister_WMDE added a comment. |
Well, according to Grafana, everything (constraint check upper runtime, number of SPARQL queries, SPARQL HTTP errors, etc.) is back to normal levels now…
I don’t think we should directly pass 429/403 errors from the query service to the client: there’s no reason to skip all other constraint checks just because there are problems with the query service. We might want to throttle constraint checks directly as well, but that’s a different issue.
But if we get HTTP 429 from WDQS, perhaps we should temporarily disable SPARQL for all requests (act as if it had not been configured), to avoid a hard ban?
And I still don’t understand how this error started – there was someone spamming wbcheckconstraints (apparently), but the first problems started earlier than that, so throttling wbcheckconstraints might not help to prevent whatever first caused the issue to occur.
Cc: Jc86035, Bugreporter, Liuxinyu970226, Nikki, MisterSynergy, Jneubert, Lucas_Werkmeister_WMDE, Aklapper, Smalyshev, Lahi, Gq86, GoranSMilovanovic, QZanden, EBjune, merbst, LawExplorer, Agabi10, Jonas, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
