Hi all,
We experienced WDQS service disruptions on 2020/07/23. As a result there was a full outage (inability to respond to all queries) for a period of several minutes, and a more extended period of intermittently degraded service (inability to respond to a subset of queries) for 1-2 hours.
The full incident report is available here: https://wikitech.wikimedia.org/wiki/Incident_documentation/20200723-wdqs-out...
Ultimately, we traced the proximate cause to a series of non-performant queries, which caused a deadlock in blazegraph, the backend for WDQS. We have placed a temporary block on the IP address in question and are taking steps to better define service availability expectations as well as processes to make detection of these events more streamlined going forward.
They must have queried Q1 ;-)
Thad https://www.linkedin.com/in/thadguidry/
On Fri, Jul 24, 2020 at 2:19 PM Ryan Kemper rkemper@wikimedia.org wrote:
Hi all,
We experienced WDQS service disruptions on 2020/07/23. As a result there was a full outage (inability to respond to all queries) for a period of several minutes, and a more extended period of intermittently degraded service (inability to respond to a subset of queries) for 1-2 hours.
The full incident report is available here: https://wikitech.wikimedia.org/wiki/Incident_documentation/20200723-wdqs-out...
Ultimately, we traced the proximate cause to a series of non-performant queries, which caused a deadlock in blazegraph, the backend for WDQS. We have placed a temporary block on the IP address in question and are taking steps to better define service availability expectations as well as processes to make detection of these events more streamlined going forward. _______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 7/24/20 3:18 PM, Ryan Kemper wrote:
Hi all,
We experienced WDQS service disruptions on 2020/07/23. As a result there was a full outage (inability to respond to all queries) for a period of several minutes, and a more extended period of intermittently degraded service (inability to respond to a subset of queries) for 1-2 hours.
The full incident report is available here: https://wikitech.wikimedia.org/wiki/Incident_documentation/20200723-wdqs-out...
Ultimately, we traced the proximate cause to a series of non-performant queries, which caused a deadlock in blazegraph, the backend for WDQS. We have placed a temporary block on the IP address in question and are taking steps to better define service availability expectations as well as processes to make detection of these events more streamlined going forward.
What was the problem query?
I ask because I would like to try it against our Wikidata endpoint at: https://wikidata.demo.openlinksw.com/sparql .
We have an "Anytime Query" feature designed for these kinds of problems, hence the vested interest in these kinds of problem queries.
See https://phabricator.wikimedia.org/T242453 linked on the report page
On Sun, Jul 26, 2020 at 6:55 PM Kingsley Idehen kidehen@openlinksw.com wrote:
On 7/24/20 3:18 PM, Ryan Kemper wrote:
Hi all,
We experienced WDQS service disruptions on 2020/07/23. As a result there was a full outage (inability to respond to all queries) for a period of several minutes, and a more extended period of intermittently degraded service (inability to respond to a subset of queries) for 1-2 hours.
The full incident report is available here:
https://wikitech.wikimedia.org/wiki/Incident_documentation/20200723-wdqs-out...
Ultimately, we traced the proximate cause to a series of non-performant queries, which caused a deadlock in blazegraph, the backend for WDQS. We have placed a temporary block on the IP address in question and are taking steps to better define service availability expectations as well as processes to make detection of these events more streamlined going forward.
What was the problem query?
I ask because I would like to try it against our Wikidata endpoint at: https://wikidata.demo.openlinksw.com/sparql .
We have an "Anytime Query" feature designed for these kinds of problems, hence the vested interest in these kinds of problem queries.
-- Regards,
Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers
Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com
Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen
Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 7/26/20 1:00 PM, Egon Willighagen wrote:
See https://phabricator.wikimedia.org/T242453%C2%A0linked on the report page
That doesn't take directly to a SPARQL query. I just want the SPARQL query.
Kingsley
On Sun, Jul 26, 2020 at 6:55 PM Kingsley Idehen <kidehen@openlinksw.com mailto:kidehen@openlinksw.com> wrote:
On 7/24/20 3:18 PM, Ryan Kemper wrote: > Hi all, > > We experienced WDQS service disruptions on 2020/07/23. As a result > there was a full outage (inability to respond to all queries) for a > period of several minutes, and a more extended period of > intermittently degraded service (inability to respond to a subset of > queries) for 1-2 hours. > > The full incident report is available here: > https://wikitech.wikimedia.org/wiki/Incident_documentation/20200723-wdqs-outage > > Ultimately, we traced the proximate cause to a series of > non-performant queries, which caused a deadlock in blazegraph, the > backend for WDQS. We have placed a temporary block on the IP address > in question and are taking steps to better define service availability > expectations as well as processes to make detection of these events > more streamlined going forward. What was the problem query? I ask because I would like to try it against our Wikidata endpoint at: https://wikidata.demo.openlinksw.com/sparql . We have an "Anytime Query" feature designed for these kinds of problems, hence the vested interest in these kinds of problem queries. -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Home Page: http://www.openlinksw.com Community Support: https://community.openlinksw.com Weblogs (Blogs): Company Blog: https://medium.com/openlink-software-blog Virtuoso Blog: https://medium.com/virtuoso-blog Data Access Drivers Blog: https://medium.com/openlink-odbc-jdbc-ado-net-data-access-drivers Personal Weblogs (Blogs): Medium Blog: https://medium.com/@kidehen Legacy Blogs: http://www.openlinksw.com/blog/~kidehen/ http://kidehen.blogspot.com Profile Pages: Pinterest: https://www.pinterest.com/kidehen/ Quora: https://www.quora.com/profile/Kingsley-Uyi-Idehen Twitter: https://twitter.com/kidehen Google+: https://plus.google.com/+KingsleyIdehen/about LinkedIn: http://www.linkedin.com/in/kidehen Web Identities (WebID): Personal: http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i : http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this _______________________________________________ Wikidata mailing list Wikidata@lists.wikimedia.org <mailto:Wikidata@lists.wikimedia.org> https://lists.wikimedia.org/mailman/listinfo/wikidata-- Hi, do you like citation networks? Already 51% of all citations are available https://i4oc.org/ available for innovative new uses https://twitter.com/hashtag/acs2ioc. Join me in asking the American Chemical Society to join the Initiative for Open Citations too https://www.change.org/p/asking-the-american-chemical-society-to-join-the-initiative-for-open-citations. SpringerNature, the RSC and many others already did https://i4oc.org/#publishers.
E.L. Willighagen Department of Bioinformatics - BiGCaT Maastricht University (http://www.bigcat.unimaas.nl/) Homepage: http://egonw.github.com/ Blog: http://chem-bla-ics.blogspot.com/ PubList: https://www.zotero.org/egonw ORCID: 0000-0001-7542-0286 http://orcid.org/0000-0001-7542-0286 ImpactStory: https://impactstory.org/u/egonwillighagen
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata