# Delayed-allocation not working as I thought it should
**URL:** https://discuss.elastic.co/t/delayed-allocation-not-working-as-i-thought-it-should/76457
**Category:** Elasticsearch
**Created:** [February 24, 2017, 11:07pm UTC](https://discuss.elastic.co/t/delayed-allocation-not-working-as-i-thought-it-should/76457 "2017-02-24T23:07:28Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@Jennifer\_Fountain](https://discuss.elastic.co/u/Jennifer_Fountain)
#### Post date: [February 24, 2017, 11:07pm UTC](https://discuss.elastic.co/t/delayed-allocation-not-working-as-i-thought-it-should/76457/1 "2017-02-24T23:07:28Z")
We are seeing an issue with our AWS cluster. If we lose a node, the entire cluster becomes unresponsive. I set this - index.unassigned.node\_left.delayed\_timeout": "0" - but still doesn't help.
Is there something else that I need to set? If we lose a node, our cluster should not go unresponsive for several seconds (Or at least I wouldn't think it should. This was not the behavior in 1.5 ☹
Thank you!
Jenn
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 26, 2017, 8:44am UTC](https://discuss.elastic.co/t/delayed-allocation-not-working-as-i-thought-it-should/76457/2 "2017-02-26T08:44:05Z")
What version are you on?
---
### Author:  [@Jennifer\_Fountain](https://discuss.elastic.co/u/Jennifer_Fountain)
#### Post date: [February 26, 2017, 2:10pm UTC](https://discuss.elastic.co/t/delayed-allocation-not-working-as-i-thought-it-should/76457/3 "2017-02-26T14:10:40Z")
We tested with 2.4.1 and 5.0.1. Both has similar results.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 26, 2017, 2:11pm UTC](https://discuss.elastic.co/t/delayed-allocation-not-working-as-i-thought-it-should/76457/4 "2017-03-26T14:11:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.