Topic on Help talk:CirrusSearch

Hi,

I believe it is working. If I change the config to an invalid search it fails and correct it , it works

$wgCirrusSearchServers = [ [ 'host' => "192.168.1.blahblah", 'port' => 31130 ]  ];

My expectation, which may be incorrect, was that I could type in a subheading e.g. "Cors" and the page containing ==Cors== would return the page in the search

Here is my set up

Thanks

LocalSettings

# This is the elastic search config

# Dont forget kubebernetes

wfLoadExtension( 'Elastica' );

wfLoadExtension('CirrusSearch');

#$wgDisableSearchUpdate = true;

$wgCirrusSearchServers = [ [ 'host' => "192.168.1.70", 'port' => 31130 ]  ];

$wgSearchType = 'CirrusSearch';

Add this to LocalSettings.php:

wfLoadExtension( 'Elastica' );

wfLoadExtension( 'CirrusSearch' );

$wgDisableSearchUpdate = true;

Add this elastic search endpoint or points

$wgCirrusSearchServers = [ 'elasticsearch0', 'elasticsearch1' ];

your elasticsearch index:

php $MW_INSTALL_PATH/extensions/CirrusSearch/maintenance/UpdateSearchIndexConfig.php

Now remove $wgDisableSearchUpdate = true from LocalSettings.php.  Updates should start heading to Elasticsearch.

Next bootstrap the search index by running:

php $MW_INSTALL_PATH/extensions/CirrusSearch/maintenance/ForceSearchIndex.php --skipLinks --indexOnSkip

php $MW_INSTALL_PATH/extensions/CirrusSearch/maintenance/ForceSearchIndex.php --skipParse

I am using elasticsearch 6.5.4

Hi,

It seems to me that the Manual:Job_queue might not be properly configured. CirrusSearch relies on it to ship the documents to elasticsearch and if it's not properly configured the indices might remain empty.