We are moving all internal traffics away from the full graph and kartotherian appears to still be using the full graph via the envoy listener on port 6009.
AC:
- kartotherian is using the wdqs-internal-main endpoint (port 6041)
We are moving all internal traffics away from the full graph and kartotherian appears to still be using the full graph via the envoy listener on port 6009.
AC:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T335067 Epic: Wikidata Query Service stabilization | |||
| Resolved | BTracy-WMF | T337013 [Epic] Splitting the graph in WDQS | |||
| Open | None | T374453 [EPIC] Migration of traffic to new Split Endpoints for WDQS | |||
| Resolved | RKemper | T379023 Create WDQS split endpoints for internal traffic and reconfigure clients to use the new endpoints | |||
| Resolved | dcausse | T388860 Kartotherian should use wdqs-internal-main |
Change #1127856 had a related patch set uploaded (by DCausse; author: DCausse):
[operations/deployment-charts@master] kartotherian: use wdqs-internal-main
Change #1127856 merged by Elukey:
[operations/deployment-charts@master] kartotherian: use wdqs-internal-main
Deployed to staging. @Jgiannelos when you have a moment ping me so we can do a sanity check, and then I'll roll it out to prod.
Change #1128430 had a related patch set uploaded (by Elukey; author: Elukey):
[operations/deployment-charts@master] kartotherian: update statsd's config ttl
Change #1128430 merged by Elukey:
[operations/deployment-charts@master] kartotherian: update statsd's config ttl
Deployed to production, Kartotherian should use the internal endpoint now. @dcausse lemme know if it is ok now :)
seems to be working I see successful kartotherian requests to the new internal-main endpoint, the last one on the old internal-full was from 2025-03-17T15:30:22. Thanks!