# Elasticsearch 8 no longer throws Http Error 429
**URL:** https://discuss.elastic.co/t/elasticsearch-8-no-longer-throws-http-error-429/347237
**Category:** Elasticsearch
**Created:** [November 15, 2023, 4:01pm UTC](https://discuss.elastic.co/t/elasticsearch-8-no-longer-throws-http-error-429/347237 "2023-11-15T16:01:30Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@melchiorGr](https://discuss.elastic.co/u/melchiorGr)
#### Post date: [November 15, 2023, 4:01pm UTC](https://discuss.elastic.co/t/elasticsearch-8-no-longer-throws-http-error-429/347237/1 "2023-11-15T16:01:30Z")
Our customers are running ES-8.x solely for our app on dedicated hardware, but since upgrade from Elastichsearch Server 7.13.x to Server 8.x indexing requests do no longer produce Http Response code 429 (which is recoverable). Instead the requests just take longer and eventually the Socket Times out.
Is there a way to make the Elasticsearch server return 429 earlier (say after a timeout) or do I just increase the socket timeout to as long as I am willing to wait?
It would be also nice to obtain a warning when the load goes up too much (rather than a sudden SocketTimeout).
Thanks for suggestions
Melchior
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [December 13, 2023, 4:01pm UTC](https://discuss.elastic.co/t/elasticsearch-8-no-longer-throws-http-error-429/347237/2 "2023-12-13T16:01:38Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.