This is the weekly update from the Search Platform team for the week starting 2019-01-07. As always, feedback and questions welcome. == Discussions == === Search === * David discovered an issue with the click-through rate on one of the Search dashboards for mobile apps [0] and enlisted Chelsy's help in fixing it quickly (done!) [1] * Mathew worked on increasing the number of shards for enwiki_general [2] * David helped to augmenting the list of known clusters using cluster conf for Mjolnir [3] * David updated the completion suggester: TP50 [Top percentile 50%] was increased from 9ms to 24ms [4] * The Search team worked on supporting searching multiple filetypes at once, based on input from the Multimedia team [5] * David and Mathew worked on allowing ElasticSearch machines to be able to communicate with each other on port 9500 and 9700 [6] * We found that most of the dashboards in grafana are designed to have a cluster per DC, and we needed to refactor them so that we can select a specific cluster (by adding chi, psi and omega selectors) [7] * The multi-instance support code added for ExternalIndex was designed without the group+replica concepts in mind, so we fixed ExternalIndex to support groups & replica topology [8] * There was a recent spike of fatal timeouts from API search suggestions (prefixsearch) that caused a number of user queries to become stalled for 60 seconds and then receive a generic error page without any results. We fixed this by merging a patch for language detection to not be run when rewriting is not enabled [9] === WDQS === * We have added a new keyboard shortcuts to WDQS UI, for those systems where Ctrl-Space is already taken - Ctrl-Alt-Space and Alt-Enter [10] * Stas found an issue where the WDQS puppet/hiera configs were too distributed, Mathew and Gehel worked on it with assistance from SRE (thanks!) [11] * Our database in WDQS seems to hit Blazegraph internal limits, which requires some careful work of rearranging the data to stay away from the limit. This work now has started [12] * Stas have fixed an issue where a large update could crash Updater [13] * Stas have fixed an issue where due to database replication delay, Updater could read an old version of the data from Wikidata [14] * Stas fixed an issue where SERVICE SILENT construct was producing errors despite standards saying it should not do that [15] [0] http://discovery.wmflabs.org/metrics/#app_events [1] https://phabricator.wikimedia.org/T211306 [2] https://phabricator.wikimedia.org/T212224 [3] https://phabricator.wikimedia.org/T211752 [4] https://phabricator.wikimedia.org/T212768 [5] https://phabricator.wikimedia.org/T212776 [6] https://phabricator.wikimedia.org/T212434 [7] https://phabricator.wikimedia.org/T211956 [8] https://phabricator.wikimedia.org/T212120 [9] https://phabricator.wikimedia.org/T212455 [10] https://phabricator.wikimedia.org/T203320 [11] https://phabricator.wikimedia.org/T210431 [12] https://phabricator.wikimedia.org/T213210 [13] https://phabricator.wikimedia.org/T210235 [14] https://phabricator.wikimedia.org/T210901 [15] https://phabricator.wikimedia.org/T196859 ---- Subscribe to receive on-wiki (or opt-in email) notifications of the Discovery weekly update. https://www.mediawiki.org/wiki/Newsletter:Discovery_Weekly The archive of all past updates can be found on MediaWiki.org: https://www.mediawiki.org/wiki/Discovery/Status_updates Interested in getting involved? See tasks marked as "Easy" or "Volunteer needed" in Phabricator. [1] https://phabricator.wikimedia.org/maniphest/query/qW51XhCCd8.7/#R [2] https://phabricator.wikimedia.org/maniphest/query/5KEPuEJh9TPS/#R Yours, Chris Koerner (he/him) Community Relations Specialist Wikimedia Foundation