Topic on Extension talk:CirrusSearch

JobQueue related (CirrusSearch updates require the JobQueue to be setup properly)

MediaWiki: 1.35.2

CirrusSearch: 6.5.4 (203237e) 03:44, 9 May 2021

Elastica: 6.1.3 (8af6b45) 21:04, 9 May 2021

Elasticsearch: 6.5.4

I've built the search index, and it shows that it ran without any errors:

root@test-snipped-wiki-1:/var/www/wikis/a# php /var/www/mediawiki_shared/extensions/CirrusSearch/maintenance/ForceSearchIndex.php --skipLinks --indexOnSkip --conf ./LocalSettings.php 

[snipped] Indexed 9 pages ending at 10 at 53/second

[...]

Indexed a total of 1616 pages at 103/second

root@test-snipped-wiki-1:/var/www/wikis/a# php /var/www/mediawiki_shared/extensions/CirrusSearch/maintenance/ForceSearchIndex.php --skipParse --conf LocalSettings.php 

[snipped] Indexed 48 pages ending at 50 at 49/second

[...]
Indexed a total of 1616 pages at 72/second




However, all my indices are empty


```

# curl -XGET localhost:9200/_cat/indices

green open wiki_a_general_first     ZYIVvSdQS4C6czO9MajjqQ 4 0  0 0  1kb  1kb

green open mw_cirrus_metastore_first 33OLZIV4TfCiv4JmqcIDYA 1 0 27 6 16kb 16kb

green open wiki_a_content_first     uJkfN6K4S_ytm1cv__9QKw 4 0  0 0  1kb  1kb

green open wiki_a_archive_first     F_ZvMuQBR6SxTtvXtT232A 4 0  0 0  1kb  1kb

```


Elasticsearch is running on the same server as MediaWiki, and I have the following on my LocalSettings.php:


```

wfLoadExtension( 'Elastica' );

wfLoadExtension( 'CirrusSearch' );

$wgSearchType = 'CirrusSearch';

$wgCirrusSearchIndexBaseName =  'wiki_a';

```


Not sure what's going on, if I go to a page and add ?action=cirrusdump I get an empty JSON array `[]`, and all my search results are empty.

Hi,

CirrusSearch index updates rely on the MediaWiki jobqueue and it's possible that the index requests are kept there or even failed.

If the documents are kept in the jobqueue they should appear with mwscript showJobs.php --group.

If this is all empty then perhaps there were some failures and you should check the mediawiki and elasticsearch logs.

Ah yes, seems you're correct! There was an issue in our deploy script that was preventing the job runner from booting up. Have only upgraded our test environment so didn't notice anything with lack of emails or anything else fired off by that system. Thanks!