Server issue Rebuild search index not working after upgrading to XF2.3.4

[Sumanta0018]

Hi,
just like XF2.3.0, I'm again facing Rebuild search index failure on XF 2.3.4 because of high memory use.

here is the log:

Server error log

• XFES\Elasticsearch\BulkRequestException: Elasticsearch indexing error: Elasticsearch bulk action error (first error: [conversation-1] index [technofi_su.....] blocked by: [TOO_MANY_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block]
• src/addons/XFES/Elasticsearch/Api.php:487
• Generated by: TechnoFino
• Nov 1, 2024 at 7:28 PM

Stack trace​

#0 src/addons/XFES/Elasticsearch/Api.php(237): XFES\Elasticsearch\Api->bulkRequest('{"index":{"_ind...')
#1 src/addons/XFES/Search/Source/Elasticsearch.php(84): XFES\Elasticsearch\Api->indexBulk(Array)
#2 src/addons/XFES/Search/Source/Elasticsearch.php(59): XFES\Search\Source\Elasticsearch->flushBulkIndexing()
#3 src/XF/Search/Search.php(66): XFES\Search\Source\Elasticsearch->index(Object(XF\Search\IndexRecord))
#4 src/addons/SV/SearchImprovements/XF/Search/SearchPatch.php(119): XF\Search\Search->index('conversation', Object(XF\Entity\ConversationMaster), true)
#5 src/XF/Search/Search.php(89): SV\SearchImprovements\XF\Search\SearchPatch->index('conversation', Object(XF\Entity\ConversationMaster))
#6 src/XF/Search/Search.php(126): XF\Search\Search->indexEntities('conversation', Object(XF\Mvc\Entity\ArrayCollection))
#7 src/XF/Job/SearchRebuild.php(69): XF\Search\Search->indexRange('conversation', 0, 500)
#8 src/XF/Job/Manager.php(275): XF\Job\SearchRebuild->run(8)
#9 src/XF/Job/Manager.php(205): XF\Job\Manager->runJobInternal(Array, 8)
#10 src/XF/Job/Manager.php(121): XF\Job\Manager->runJobEntry(Array, 8)
#11 src/XF/Admin/Controller/ToolsController.php(146): XF\Job\Manager->runByIds(Array, 8)
#12 src/XF/Mvc/Dispatcher.php(362): XF\Admin\Controller\ToolsController->actionRunJob(Object(XF\Mvc\ParameterBag))
#13 src/XF/Mvc/Dispatcher.php(264): XF\Mvc\Dispatcher->dispatchClass('XF:Tools', 'RunJob', Object(XF\Mvc\RouteMatch), Object(Truonglv\Watermark\XF\Admin\Controller\ToolsController), NULL)
#14 src/XF/Mvc/Dispatcher.php(121): XF\Mvc\Dispatcher->dispatchFromMatch(Object(XF\Mvc\RouteMatch), Object(Truonglv\Watermark\XF\Admin\Controller\ToolsController), NULL)
#15 src/XF/Mvc/Dispatcher.php(63): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#16 src/XF/App.php(2826): XF\Mvc\Dispatcher->run()
#17 src/XF.php(806): XF\App->run()
#18 admin.php(15): XF::runApp('XF\\Admin\\App')
#19 {main}

Request state​

array(4) {
["url"] => string(34) "/community/admin.php?tools/run-job"
["referrer"] => string(144) "https://www.technofino.in/community/admin.php?tools/run-job&only_id=6889250&_xfRedirect=/community/admin.php?tools/rebuild&success=1"
["_GET"] => array(1) {
["tools/run-job"] => string(0) ""
}
["_POST"] => array(3) {
["_xfRedirect"] => string(69) "https://www.technofino.in/community/admin.php?tools/rebuild&success=1"
["_xfToken"] => string(8) "********"
["only_ids"] => string(7) "6889250"
}
}
Possible solutions?

And this is affecting many functions of website, like users can't see their posted contents from their profile (your content option).

 

[Chris D]

TOO_MANY_REQUESTS/12/disk usage exceeded

This is not memory (RAM) usage, it is disk space.

If your main disk is more than 90% utilised (by default), Elasticsearch will stop indexing activity.

You will need to increase disk space allocation, reconfigure the Elasticsearch limits or free up disk space.

 

[Sumanta0018]

This is not memory (RAM) usage, it is disk space.

If your main disk is more than 90% utilised (by default), Elasticsearch will stop indexing activity.

You will need to increase disk space allocation, reconfigure the Elasticsearch limits or free up disk space.

Thanks Chris

 

[Sumanta0018]

This is not memory (RAM) usage, it is disk space.

If your main disk is more than 90% utilised (by default), Elasticsearch will stop indexing activity.

You will need to increase disk space allocation, reconfigure the Elasticsearch limits or free up disk space.

I just freed up some space by deleting old backup files. Now, available disk space is over 40 GB, but I'm still facing the same issue.

 

[Chris D]

This is what Elasticsearch was reporting in the original error, that it was disk space.

If you’re still seeing the same error, we are just reporting what elasticsearch is reporting.

We have no control over how elasticsearch is configured. That would be down to you or your host