# How to lock the current allocation state
**URL:** https://discuss.elastic.co/t/how-to-lock-the-current-allocation-state/248072
**Category:** Elasticsearch
**Created:** [September 9, 2020, 8:54pm UTC](https://discuss.elastic.co/t/how-to-lock-the-current-allocation-state/248072 "2020-09-09T20:54:18Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@UDixit](https://discuss.elastic.co/u/UDixit)
#### Post date: [September 9, 2020, 8:54pm UTC](https://discuss.elastic.co/t/how-to-lock-the-current-allocation-state/248072/1 "2020-09-09T20:54:18Z")
When `cluster.routing.rebalance.enable` is set to none, I understand that we are lokcing the current allocation state of the cluster. i.e. the currenlty allocated shards will not relocate to other nodes.
But what happens is a new index is created? will its shards remain unassigned because allocation.enable is set to none?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [September 9, 2020, 11:44pm UTC](https://discuss.elastic.co/t/how-to-lock-the-current-allocation-state/248072/2 "2020-09-09T23:44:18Z")
Can I ask what problem are you trying to solve with this approach?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [October 7, 2020, 11:44pm UTC](https://discuss.elastic.co/t/how-to-lock-the-current-allocation-state/248072/3 "2020-10-07T23:44:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.