@Gehel Given that this is approved by Jaime and in plan pending FDC approval do you want close it out and re-open when we finalize on hardware or do you want to keep this open?

@mark Yes, lets move forward with this. thanks

Approved

Approved

Certainly not me :)

I'd recommend reaching out to Sheree or Wes to help out with this

This will likely fit under the strategic budget so we'll need a brief narrative about going default on Wikipedia and any other projects to explain the increase of machines.

In my previous life managing search clusters we split our corpus by geographic location, then function (full text, prefix, etc) and then partitioned the data to fit into the nodes that we had available (P1, P2, etc). This allowed us to get much more predictable estimates for query patterns relative to year over year traffic trends. Since languages aren't bound tightly to geographic locations language becomes the next best estimate. Given that #3 is the most enticing following by #2.

If we have lost a DC then we should not be doing maintenance on a node. Stability is key then. I'm used to running in an n+1 hardware layout where any of your DC's can fall over and the other(s) can take total traffic while running slightly hot. Then it doesn't really matter which one gets the traffic and your users are happy.

I agree with Gabriel that having https://phabricator.wikimedia.org/T113540 informal and for feedback would be best. The phab task has already been really helpful to get some of that feedback. We can think about it un-conference style.

Interest in the following

Data remains unchanged. Re-opening.

Approved

Approved

@Jdlrobson @Catrope - do you have any blocking bugs around search? Eager to hear from any community devs as well

That would be useful data to have. @Deskana, are we already tracking it elsewhere? let's avoid duplication if so

Approved

@dr0ptp4kt: I'd like to meet this week to discuss. Can you make sure you have your team discussion before?

@bearND @dr0ptp4kt @BGerstle-WMF @Jdlrobson @Catrope - would love to get feedback from you guys about what improvements discovery can make to the search API to make development of products easier and faster

Resolving per https://lists.wikimedia.org/pipermail/wikitech-l/2015-September/083277.html

Very happy with the updates. I've been the updated docs actively. Let's resolve.

thank you @Dzahn

Right now were focusing our conversations using discovery@ and traffic on maps-l is really small.

@Ironholds yes, we'll need this to complete our picture of the maps pipeline.

Let's move this to https://www.mediawiki.org/wiki/Talk:Maps as this task is not actionable right now

Let's rename please

Thanks @Yurik. Usually I would think about these kind of metrics being in ganglia or grafana but @MaxSem tells me that we can't connect those tools to a Varnish stream. Let's work with @Ironholds to find out what they would need in order to surface these data points. This request would cover the server side metrics and is separate from our existing client side metric KPI's. Implementing these should not block launch.

@Dzahn, let's just rename the lists so that we can keep the archives

@Dzahn, looks like you this patch set adds "tfinc" instead of "tomasz" I'd mention that in CR but gerrit is not letting me in

Checking in to see when we plan to have this live for our alpha and beta users. I know we have some design back and forth but i'm curious if we have a time that were targeting to get this out for testing. thanks

I could see some interesting follow ups to this.

It's fine for now. We'll iterate as we learn about usage.

@Yurik - can you move https://www.mediawiki.org/wiki/Maps#Production_maps_cluster to wikitech and update as needed?

I've made lots of updates to https://www.mediawiki.org/wiki/Maps and https://etherpad.wikimedia.org/p/maps-email

Happy to summarize

@MaxSem @Yurik - Since both of you are going to speak with MapBox can you find out how they measure this? I'm looking for some standard industry practice. We don't want to have analyze every single zoom, pinch, etc but instead have a higher level of view of what's happening

I mailed Juliet at comms to give her a heads up about this. Not looking for any direct support them as we'll likely focus on-wiki and mailing lists