﻿---
title: Allow Elasticsearch to allocate the data in the system
description: The allocation of data in an Elasticsearch deployment can be controlled using the enable cluster allocation configuration. In certain circumstances users...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4400/troubleshoot/elasticsearch/allow-all-cluster-allocation
products:
  - Elasticsearch
---

# Allow Elasticsearch to allocate the data in the system
The allocation of data in an Elasticsearch deployment can be controlled using the [enable cluster allocation configuration](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings#cluster-routing-allocation-enable). In certain circumstances users might want to temporarily disable or restrict the allocation of data in the system.
Forgetting to re-allow all data allocations can lead to unassigned shards.
In order to (re)allow all data to be allocated follow these steps:
<tab-set>
  <tab-item title="Elastic Cloud Hosted">
    In order to get the shards assigned we’ll need to change the value of the [configuration](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings#cluster-routing-allocation-enable) that restricts the assignemnt of the shards to allow all shards to be allocated.We’ll achieve this by inspecting the system-wide `cluster.routing.allocation.enable` [cluster setting](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) and changing the configured value to `all`.**Use Kibana**
    1. Log in to the [Elastic Cloud console](https://cloud.elastic.co?page=docs&placement=docs-body).
    2. On the **Hosted deployments** panel, click the name of your deployment.
       <note>
       If the name of your deployment is disabled your Kibana instances might be unhealthy, in which case contact [Elastic Support](https://support.elastic.co). If your deployment doesn’t include Kibana, all you need to do is [enable it first](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4400/deploy-manage/deploy/elastic-cloud/access-kibana).
       </note>
    3. Open your deployment’s side navigation menu (placed under the Elastic logo in the upper left corner) and go to **Dev Tools > Console**.
       ![](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4400/troubleshoot/images/elasticsearch-reference-kibana-console.png)

    1. Inspect the `cluster.routing.allocation.enable` [cluster setting](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings):
       ```json
       ```
       The response will look like this:
       ```json
       {
         "persistent": {
           "cluster.routing.allocation.enable": "none" 
         },
         "transient": {}
       }
       ```
    2. [Change](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) the [configuration](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings#cluster-routing-allocation-enable) value to allow all the data in the system to be fully allocated:
       ```json

       {
         "persistent" : {
           "cluster.routing.allocation.enable" : "all" <1>
         }
       }
       ```
  </tab-item>

  <tab-item title="Self-managed">
    In order to get the shards assigned we’ll need to change the value of the [configuration](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings#cluster-routing-allocation-enable) that restricts the assignemnt of the shards to allow all shards to be allocated.We’ll achieve this by inspecting the system-wide `cluster.routing.allocation.enable` [cluster setting](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) and changing the configured value to `all`.
    1. Inspect the `cluster.routing.allocation.enable` [cluster setting](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings):
       ```json
       ```
       The response will look like this:
       ```json
       {
         "persistent": {
           "cluster.routing.allocation.enable": "none" 
         },
         "transient": {}
       }
       ```
    2. [Change](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) the [configuration](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/cluster-level-shard-allocation-routing-settings#cluster-routing-allocation-enable) value to allow all the data in the system to be fully allocated:
       ```json

       {
         "persistent" : {
           "cluster.routing.allocation.enable" : "all" <1>
         }
       }
       ```
  </tab-item>
</tab-set>