Page MenuHomePhabricator

Elastica/CirrusSearch related errors on initial start-up
Closed, ResolvedPublic

Description

The following error was reported on the wikibaseug mailng list:

wikibase_1         | 		Validating my_wiki_general alias...alias is free...corrected
wikibase_1         | 		Validating my_wiki alias...alias not already assigned to this index...corrected
wikibase_1         | 		Updating tracking indexes...
wikibase_1         | Unexpected Elasticsearch failure.
wikibase_1         | Elasticsearch failed in an unexpected way. This is always a bug in CirrusSearch.
wikibase_1         | Error type: Elastica\Exception\Bulk\ResponseException
wikibase_1         | Message: unknown: Error in one or more bulk request actions:
wikibase_1         |
wikibase_1         | index: /mw_cirrus_metastore_first/mw_cirrus_metastore/version-my_wiki_content caused blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];
wikibase_1         | index: /mw_cirrus_metastore_first/mw_cirrus_metastore/version-my_wiki_general caused blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];
wikibase_1         | index: /mw_cirrus_metastore_first/mw_cirrus_metastore/version-my_wiki_archive caused blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];
wikibase_1         |
wikibase_1         | Trace:
wikibase_1         | #0 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Bulk.php(359): Elastica\Bulk->_processResponse(Object(Elastica\Response))
wikibase_1         | #1 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Client.php(361): Elastica\Bulk->send()
wikibase_1         | #2 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Index.php(182): Elastica\Client->addDocuments(Array, Array) 
wikibase_1         | #3 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Type.php(202): Elastica\Index->addDocuments(Array, Array)
wikibase_1         | #4 /var/www/html/extensions/CirrusSearch/includes/MetaStore/MetaVersionStore.php(70): Elastica\Type->addDocuments(Array)
wikibase_1         | #5 /var/www/html/extensions/CirrusSearch/maintenance/metastore.php(133): CirrusSearch\MetaStore \MetaVersionStore->updateAll('my_wiki') 
wikibase_1         | #6 /var/www/html/extensions/CirrusSearch/maintenance/metastore.php(95): CirrusSearch\Maintenance\Metastore->updateIndexVersion('my_wiki')
wikibase_1         | #7 /var/www/html/extensions/CirrusSearch/maintenance/updateOneSearchIndexConfig.php(301): CirrusSearch\Maintenance\Metastore->execute()
wikibase_1         | #8 /var/www/html/extensions/CirrusSearch/maintenance/updateOneSearchIndexConfig.php(270): CirrusSearch\Maintenance\UpdateOneSearchIndexConfig->updateVersions()
wikibase_1         | #9 /var/www/html/extensions/CirrusSearch/maintenance/updateSearchIndexConfig.php(61): CirrusSearch\Maintenance\UpdateOneSearchIndexConfig->execute()
wikibase_1         | #10 /var/www/html/maintenance/doMaintenance.php(99): CirrusSearch\Maintenance\UpdateSearchIndexConfig->execute()
wikibase_1         | #11 /var/www/html/extensions/CirrusSearch/maintenance/updateSearchIndexConfig.php(70): require_once('/var/www/html/m...')
wikibase_1         | #12 {main}

It can be reproduced like this:

git clone https://github.com/wmde/wikibase-docker.git
cd wikibase-docker
docker-compose up wikibase

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
JesperZedlitz updated the task description. (Show Details)
JesperZedlitz updated the task description. (Show Details)

Unfortunately I'm unable to reproduce the issue. With a clean install using the docker-compose.yml from the current master branch I'm seeing similar lines being logged, but without any errors.

wikibase_1         | 		Validating my_wiki_archive alias...alias is free...corrected
wikibase_1         | 		Updating tracking indexes...done

My best guess for now is that ElasticSearch went into read-only mode because it ran out of disk space. This would be similar to T244630 which shows similar errors.

@JesperZedlitz, could you check whether the disk space problem might apply to you?

After assigning more disk space to the virtual server it worked without problems. I guess I would never have thought of that on my own.