Elasticsearch indexing error

[MJ0730]

Started getting this error a day ago for any new posts. Looks like nothing new is being indexed.

[LIST]
[*]XFES\Elasticsearch\RequestException: Elasticsearch indexing error (queued): Unknown error (HTTP code: 429)
[*] 
[*]src/addons/XFES/Elasticsearch/Api.php:409
[*]Generated by: bigfooten28
[*] 
[*]Apr 24, 2019 at 6:10 PM
[/LIST]
Stack trace
#0 src/addons/XFES/Elasticsearch/Api.php(330): XFES\Elasticsearch\Api->request('put', 'pointsixtyfive-...', '{
    "title": ...')
#1 src/addons/XFES/Elasticsearch/Api.php(348): XFES\Elasticsearch\Api->requestFromIndex('put', 'xf/post-41408', Array)
#2 src/addons/XFES/Elasticsearch/Api.php(152): XFES\Elasticsearch\Api->requestById('put', 'post', 41408, Array)
#3 src/addons/XFES/Search/Source/Elasticsearch.php(66): XFES\Elasticsearch\Api->index('post', 41408, Array)
#4 src/XF/Search/Search.php(40): XFES\Search\Source\Elasticsearch->index(Object(XF\Search\IndexRecord))
#5 src/XF/Behavior/Indexable.php(46): XF\Search\Search->index('post', Object(XF\Entity\Post), false)
#6 src/XF.php(290): XF\Behavior\Indexable->XF\Behavior\{closure}()
#7 src/XF/Mvc/Dispatcher.php(143): XF::triggerRunOnce(true)
#8 src/XF/Mvc/Dispatcher.php(50): XF\Mvc\Dispatcher->dispatchLoop(Object(XF\Mvc\RouteMatch))
#9 src/XF/App.php(2177): XF\Mvc\Dispatcher->run()
#10 src/XF.php(390): XF\App->run()
#11 index.php(20): XF::runApp('XF\\Pub\\App')
#12 {main}

Request state
array(4) {
  ["url"] => string(95) "/xenforo/threads/air-traffic-control-specialist-trainee-faa-ato-18-allsrce-57792.2995/add-reply"
  ["referrer"] => string(120) "https://pointsixtyfive.com/xenforo/threads/air-traffic-control-specialist-trainee-faa-ato-18-allsrce-57792.2995/page-240"
  ["_GET"] => array(0) {
  }
  ["_POST"] => array(9) {
    ["message_html"] => string(219) "<p>Yeah I’ve already got an enroute class date so if zse isn’t possible then we’re out of here. I’m not really upset about that really I’m not even from here, I just want to give my squadron some heads up.</p>"
    ["attachment_hash"] => string(32) "07a7baf6fe564f7253ecba92e60f33df"
    ["attachment_hash_combined"] => string(86) "{"type":"post","context":{"thread_id":2995},"hash":"07a7baf6fe564f7253ecba92e60f33df"}"
    ["last_date"] => string(10) "1556146697"
    ["last_known_date"] => string(10) "1556146697"
    ["_xfToken"] => string(8) "********"
    ["_xfRequestUri"] => string(94) "/xenforo/threads/air-traffic-control-specialist-trainee-faa-ato-18-allsrce-57792.2995/page-240"
    ["_xfWithData"] => string(1) "1"
    ["_xfResponseType"] => string(4) "json"
  }
}

 

[Paul B]

You may want to contact your host.

429 Too Many Requests - HTTP | MDN

The HTTP 429 Too Many Requests client error response status code indicates the client has sent too many requests in a given amount of time. This mechanism of asking the client to slow down the rate of requests is commonly called "rate limiting".

developer.mozilla.org

 

[MJ0730]

Yeah. But the error is occurring trying to send info to the search index correct? There's no way I'm sending enough requests to saturate the host limit.