[12:29:34] <zpapierski>	 break
[18:46:59] <ebernhardson>	 i should learn to stop looking into things deeper, always find more broken things :(  The classic profile for prefixsearch is only returning exact matches...
[18:49:03] <ebernhardson>	 huh, no something else weird is happening. It usually works, but if you add `&cirrusDumpQuery`  it only returns one result. Even weirder...but it's a debug option and not going to look :P
[20:50:52] <justinl>	 ebernhardson Quick follow-up on your help from yesterday regarding deleting and recreating the indexes. Here's the process I've come up with today and seems to work well.
[20:50:54] <justinl>	 Delete indexes
[20:50:55] <justinl>	 php ./extensions/CirrusSearch/maintenance/UpdateSearchIndexConfig.php --startOver --indexIdentifier now --reindexAndRemoveOk
[20:50:55] <justinl>	 curl -X DELETE 'http://localhost:9200/es_wikidb_gw2_content_*'
[20:50:56] <justinl>	 Recreate indexes
[20:50:56] <justinl>	 UpdateSearchIndexConfig.php
[20:50:57] <justinl>	 Comment out $wgDisableSearchUpdate
[20:50:57] <justinl>	 ForceSearchIndex.php --skip-links --indexOnSkip
[20:50:58] <justinl>	 ForceSearchIndex.php --skipParse
[21:04:32] <ebernhardson>	 justinl: sounds reasonable
[21:24:04] <justinl>	 Based on my time testing so far, it looks like the biggest wiki takes about 60-70 minutes each for the two ForceSearchIndex.php commands while UpdateSearchIndexConfig.php takes seconds. And since the indexing only affects search until the initial indexes are created, I should be able to have a very short downtime to deploy the updated MW code with
[21:24:05] <justinl>	 CirrusSearch, Elastica, etc. and the necessary configration. We'd just need to let our users know to expect search to kinda suck for the day since the indexing will take a very long time because of the 10s of thousands of jobs that will get created in the queues, which will also impact wiki performance heavily due to our PHP-FPM perf issue, but
[21:24:05] <justinl>	 once it's done hopefully things will be much better. 
[21:26:24] <ebernhardson>	 That sounds about right, the index creation is pretty cheap and everything will "work", meaning not fail catasrophically, even if the index is empty
[21:29:42] <justinl>	 Once that's done I can focus on our MW 1.36 upgrade, which I'm praying will somehow magically resolve the PHP-FPM perf issue that started with the 1.35 upgrade. Coincidentally, when I finally deploy 1.36, I'll have to re-index!
[21:30:18] <justinl>	 Just would like to say how appreciative I am to have access to this channel and all of the help I've received here. It is most appreciated!
[21:30:32] <justinl>	 (I guess I repeated myself there...)
[21:32:35] <ebernhardson>	 no worries :) I've been answering questions on freenode/irc much longer than i've been around at wmf. It's helped me significantly in the past as well
[21:33:56] <ebernhardson>	 Err, i fail at english. But anyways awkward way to say i've had great help before from oss irc channels, glad to return the favor