# Maximum number of retries reached
**URL:** https://discuss.elastic.co/t/maximum-number-of-retries-reached/117480
**Category:** Elasticsearch
**Created:** [January 29, 2018, 2:45pm UTC](https://discuss.elastic.co/t/maximum-number-of-retries-reached/117480 "2018-01-29T14:45:37Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@bbcdenmark](https://discuss.elastic.co/u/bbcdenmark)
#### Post date: [January 29, 2018, 2:45pm UTC](https://discuss.elastic.co/t/maximum-number-of-retries-reached/117480/1 "2018-01-29T14:45:37Z")
We got 3 different environments running Elastic Search - Development, Test and Production. But recently we started to get the error " **Maximum number of retries reached**" when creating an Index from a C# program, but only in the test environment. It's a cluster with 2 nodes.
This is the exact exception thrown: "_Elasticsearch.Net.ElasticsearchClientException: Maximum number of retries reached. ---\> System.Net.WebException: The remote server returned an error: (400) Bad Request._"
I hope that someone in this group can give me a hint, what to search for?
---
### Author:  [@bbcdenmark](https://discuss.elastic.co/u/bbcdenmark)
#### Post date: [January 30, 2018, 12:35pm UTC](https://discuss.elastic.co/t/maximum-number-of-retries-reached/117480/2 "2018-01-30T12:35:24Z")
Problem is solved. It was an issue with the disk space on both servers. Looks like there is a 85% treshold setting in elastic-search configuration that caused the problem.
I could change the treshold value, but cleaning up the disk was an immediate fix
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 27, 2018, 12:35pm UTC](https://discuss.elastic.co/t/maximum-number-of-retries-reached/117480/3 "2018-02-27T12:35:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.