[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

Gehel closed this task as "Resolved". TASK DETAIL https://phabricator.wikimedia.org/T199219 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Mstyles, Gehel Cc: dcausse, Ladsgroup, akosiaris, BBlack, Aklapper, Smalyshev, Gehel, Invadibot, MPhamWMF,

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

dcausse moved this task from Needs review to To Be Deployed on the Discovery-Search (Current work) board. dcausse assigned this task to Mstyles. TASK DETAIL https://phabricator.wikimedia.org/T199219 WORKBOARD https://phabricator.wikimedia.org/project/board/1227/ EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

akosiaris added a comment. In T199219#6855641 , @Gehel wrote: > In terms of implementation in our new updater, the comment from @BBlack is the starting point: > > In T199219#4416896

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

Gehel added a comment. In terms of implementation in our new updater, the comment from @BBlack is the starting point: In T199219#4416896 , @BBlack wrote: > For this very particular case, the simplest way would be to do your

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

MPhamWMF set the point value for this task to "5". TASK DETAIL https://phabricator.wikimedia.org/T199219 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: MPhamWMF Cc: dcausse, Ladsgroup, akosiaris, BBlack, Aklapper, Smalyshev, Gehel, MPhamWMF,

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

Gehel added a comment. In T199219#6836794 , @dcausse wrote: > The new updater is currently running on the analytics network (working on getting k8s deployment reading), we could set it up to appservers-ro but I think a hole needs to be

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

MPhamWMF moved this task from Scaling to Current work on the Wikidata-Query-Service board. MPhamWMF added a project: Discovery-Search (Current work). TASK DETAIL https://phabricator.wikimedia.org/T199219 WORKBOARD https://phabricator.wikimedia.org/project/board/891/ EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

Gehel added a parent task: T244590: [Epic] Rework the WDQS updater as an event driven application. TASK DETAIL https://phabricator.wikimedia.org/T199219 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel Cc: dcausse, Ladsgroup, akosiaris, BBlack,

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

dcausse added a comment. The new updater is currently running on the analytics network (working on getting k8s deployment reading), we could set it up to appservers-ro but I think a hole needs to be open between the two networks (see similar issue in T274951

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

Gehel added a comment. The new Flink based WDQS updater (T244590 ) will mitigate the potential caching issues since it will be running centrally and not duplicate the work for each WDQS node. Since this is expected to be completed this quarter, it

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

akosiaris added a comment. For what is worth, we now have the services proxy (envoy based) with persistent connections and doing TLS on its own so any costs from switching to TLS connections to the internal LVS services will be largely mitigated. In fact, if anything I expect the latencies

[Wikidata-bugs] [Maniphest] T199219: WDQS should use internal endpoint to communicate to Wikidata

Gehel raised the priority of this task from "Low" to "High". Gehel moved this task from Operations to All WDQS-related tasks on the Wikidata-Query-Service board. Gehel added a comment. Let's reprioritize this given the recent issues we've seen. TASK DETAIL