Page MenuHomePhabricator

Hypothesis WE2.5.1: setup triple stores in eqiad
Open, Needs TriagePublic

Description

Hypothesis text

If we deploy the Blazegraph candidate replacement in eqiad and augment existing evaluation work with production WDQS traffic-replay analysis, then we will confirm that the new backend performs comparably, supports real-world SPARQL queries, and is ready for limited live-traffic exposure once the surrounding ecosystem (UI, monitoring, onboarding, and real-time index update pipeline) is prepared.

Milestones

High level implementation goals (subset of ACs defined for the hypothesis).

  • QLever and Virtuoso instances are available internally in eqiad
  • AWS tests have been fully reproduced on-prem, and augmented with full support to replay traffic from WDQS query logs.
  • We implemented, or at least prototyped, a solution to to support label and mwapi services.
  • Instances of Query UI are available for limited, internal, access to test databases.
  • Changes required to Grafana dashboards and Prometheus alerting required to support live traffic have been documented.

Event Timeline

gmodena renamed this task from Hypothesis 5.2.1: setup triple stores in eqiad to Hypothesis 2.5.1: setup triple stores in eqiad.Fri, Feb 13, 3:12 PM
gmodena renamed this task from Hypothesis 2.5.1: setup triple stores in eqiad to Hypothesis WE2.5.1: setup triple stores in eqiad.Tue, Feb 17, 12:44 PM