[06:54:11] <dcausse>	 ryankemper: thanks!
[10:52:33] <dcausse>	 lunch
[12:43:37] <inflatador>	 <o/
[12:44:19] <dcausse>	 o/
[12:45:18] <pfischer>	 o/
[13:01:25] <gehel>	 dcausse: do you know how long did the data reload on wdqs2023 took?
[13:06:59] <dcausse>	 gehel: it's still catching up on lag but the blazegraph import took 7days and 15hours (T241128) 
[13:07:00] <stashbot>	 T241128: EPIC: Reduce the time needed to do the initial WDQS import - https://phabricator.wikimedia.org/T241128
[13:07:32] <gehel>	 and that was for how many triples?
[13:07:39] <dcausse>	 15.9B
[13:08:35] <dcausse>	 for the catchup I think you can add ~1.5days
[13:08:54] <dcausse>	 so roughly 9days to recover
[13:10:33] <dcausse>	 so even in the worscase scenario where all future triples are added to the main graph we can recover within 10days after the graph split with 20B
[13:12:42] <gehel>	 cool!
[13:18:11] <inflatador>	 dcausse I updated https://gerrit.wikimedia.org/r/c/operations/alerts/+/1043198 based on your feedback, LMK if it needs anything else
[13:20:12] <dcausse>	 inflatador: lgtm
[13:21:10] <dcausse>	 gehel: I think we should keep T367510 open til we actually create the topics
[13:21:11] <stashbot>	 T367510: Request permission to create 4 kafka topics in kafka-main (WDQS graph split) - https://phabricator.wikimedia.org/T367510
[13:26:34] <gehel>	 dcausse: re-opened!
[13:26:59] <dcausse>	 thanks!
[13:39:44] <dcausse>	 opening a dedicated port to handle internal federation sounds difficult... seems like it might need multiple tlsproxy running like what we do for elasticsearch
[14:08:02] <pfischer>	 going offline, will be back later tonight
[14:11:45] <inflatador>	 btullis dcausse Created a new patch based on David's solution to use puppet for the search platform alerts, see if this is better: https://gerrit.wikimedia.org/r/c/operations/puppet/+/1048467
[14:22:20] <dcausse>	 thanks!
[14:32:16] <inflatador>	 headed to swim class, back in ~30
[15:13:21] <dcausse>	 going offline, have a nice week-end
[15:16:05] <inflatador>	 .o/
[15:16:29] <inflatador>	 Does anyone else have trouble finding stuff on gitlab? I haven't had much luck with its search
[15:20:32] <dr0ptp4kt>	 yes. although try https://codesearch.wmcloud.org (assuming that hasn't been a problem, too). I think stuff is more indexed there as of recently. it seems like upstream is focused on search as a differentiated paid offering, although i know it's possible to put in your own search engine on a standalone floss install, too
[15:24:41] <dr0ptp4kt>	 (it seems like to have "nice" ElasticSearch advanced searching you gotta pay, although in theory anything _could_ be wired up manually on a floss install...all the usual caveats of maintaining non-supported community edition software and stuff...)
[15:26:57] <inflatador>	 dr0ptp4kt excellent, thanks! I forgot all about codesearch ;(
[15:50:09] <ebernhardson>	 \o
[16:15:27] <inflatador>	 <o/
[17:46:49] <inflatador>	 lunch, back in ~40
[18:14:47] <inflatador>	 back
[20:00:23] <inflatador>	 errand, back in ~1h
[21:03:00] <inflatador>	 back