Skip to content

Latest commit

 

History

History
437 lines (357 loc) · 14.7 KB

troubleshooting-shards-capacity-issues.md

File metadata and controls

437 lines (357 loc) · 14.7 KB
applies_to navigation_title mapped_pages
stack deployment
eck ess ece self
Shard capacity issues

Troubleshoot shard capacity health issues [troubleshooting-shards-capacity-issues]

{{es}} limits the maximum number of shards to be held per node using the cluster.max_shards_per_node and cluster.max_shards_per_node.frozen settings. The current shards capacity of the cluster is available in the health API shards capacity section.

Cluster is close to reaching the configured maximum number of shards for data nodes. [_cluster_is_close_to_reaching_the_configured_maximum_number_of_shards_for_data_nodes]

The cluster.max_shards_per_node cluster setting limits the maximum number of open shards for a cluster, only counting data nodes that do not belong to the frozen tier.

This symptom indicates that action should be taken, otherwise, either the creation of new indices or upgrading the cluster could be blocked.

If you’re confident your changes won’t destabilize the cluster, you can temporarily increase the limit using the cluster update settings API:

:::::::{tab-set}

::::::{tab-item} {{ech}} Use {{kib}}

  1. Log in to the {{ecloud}} console.

  2. On the Hosted deployments panel, click the name of your deployment.

    ::::{note} If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact Elastic Support. If your deployment doesn’t include {{kib}}, all you need to do is enable it first. ::::

  3. Open your deployment’s side navigation menu (placed under the Elastic logo in the upper left corner) and go to Dev Tools > Console.

    :::{image} /troubleshoot/images/elasticsearch-reference-kibana-console.png :alt: {{kib}} Console :screenshot: :::

  4. Check the current status of the cluster according the shards capacity indicator:

    GET _health_report/shards_capacity

    The response will look like this:

    {
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "yellow",
      "symptom": "Cluster is close to reaching the configured maximum number of shards for data nodes.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1000, <1>
          "current_used_shards": 988 <2>
        },
        "frozen": {
          "max_shards_in_cluster": 3000,
          "current_used_shards": 0
        }
      },
      "impacts": [
        ...
      ],
      "diagnosis": [
        ...
    }
  }
}
    1. Current value of the setting cluster.max_shards_per_node
    2. Current number of open shards across the cluster

  5. Update the cluster.max_shards_per_node setting with a proper value:

    PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node": 1200
  }
}

    This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or reduce your cluster’s shard count on nodes that do not belong to the frozen tier.

  6. To verify that the change has fixed the issue, you can get the current status of the shards_capacity indicator by checking the data section of the health API:

    GET _health_report/shards_capacity

    The response will look like this:

    {
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "green",
      "symptom": "The cluster has enough room to add new shards.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1000
        },
        "frozen": {
          "max_shards_in_cluster": 3000
        }
      }
    }
  }
}

  7. When a long-term solution is in place, we recommend you reset the cluster.max_shards_per_node limit.

    PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node": null
  }
}

::::::

::::::{tab-item} Self-managed Check the current status of the cluster according the shards capacity indicator:

GET _health_report/shards_capacity

The response will look like this:

{
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "yellow",
      "symptom": "Cluster is close to reaching the configured maximum number of shards for data nodes.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1000, <1>
          "current_used_shards": 988 <2>
        },
        "frozen": {
          "max_shards_in_cluster": 3000
        }
      },
      "impacts": [
        ...
      ],
      "diagnosis": [
        ...
    }
  }
}
  1. Current value of the setting cluster.max_shards_per_node
  2. Current number of open shards across the cluster

Using the cluster settings API, update the cluster.max_shards_per_node setting:

PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node": 1200
  }
}

This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or reduce your cluster’s shard count on nodes that do not belong to the frozen tier. To verify that the change has fixed the issue, you can get the current status of the shards_capacity indicator by checking the data section of the health API:

GET _health_report/shards_capacity

The response will look like this:

{
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "green",
      "symptom": "The cluster has enough room to add new shards.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1200
        },
        "frozen": {
          "max_shards_in_cluster": 3000
        }
      }
    }
  }
}

When a long-term solution is in place, we recommend you reset the cluster.max_shards_per_node limit.

PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node": null
  }
}

::::::

:::::::

Cluster is close to reaching the configured maximum number of shards for frozen nodes. [_cluster_is_close_to_reaching_the_configured_maximum_number_of_shards_for_frozen_nodes]

The cluster.max_shards_per_node.frozen cluster setting limits the maximum number of open shards for a cluster, only counting data nodes that belong to the frozen tier.

This symptom indicates that action should be taken, otherwise, either the creation of new indices or upgrading the cluster could be blocked.

If you’re confident your changes won’t destabilize the cluster, you can temporarily increase the limit using the cluster update settings API:

:::::::{tab-set}

::::::{tab-item} {{ech}} Use {{kib}}

  1. Log in to the {{ecloud}} console.

  2. On the Hosted deployments panel, click the name of your deployment.

    ::::{note} If the name of your deployment is disabled your {{kib}} instances might be unhealthy, in which case please contact Elastic Support. If your deployment doesn’t include {{kib}}, all you need to do is enable it first. ::::

  3. Open your deployment’s side navigation menu (placed under the Elastic logo in the upper left corner) and go to Dev Tools > Console.

    :::{image} /troubleshoot/images/kibana-console.png :alt: {{kib}} Console :screenshot: :::

  4. Check the current status of the cluster according the shards capacity indicator:

    GET _health_report/shards_capacity

    The response will look like this:

    {
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "yellow",
      "symptom": "Cluster is close to reaching the configured maximum number of shards for frozen nodes.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1000
        },
        "frozen": {
          "max_shards_in_cluster": 3000, <1>
          "current_used_shards": 2998 <2>
        }
      },
      "impacts": [
        ...
      ],
      "diagnosis": [
        ...
    }
  }
}
    1. Current value of the setting cluster.max_shards_per_node.frozen
    2. Current number of open shards used by frozen nodes across the cluster

  5. Update the cluster.max_shards_per_node.frozen setting:

    PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node.frozen": 3200
  }
}

    This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or reduce your cluster’s shard count on nodes that belong to the frozen tier.

  6. To verify that the change has fixed the issue, you can get the current status of the shards_capacity indicator by checking the data section of the health API:

    GET _health_report/shards_capacity

    The response will look like this:

    {
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "green",
      "symptom": "The cluster has enough room to add new shards.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1000
        },
        "frozen": {
          "max_shards_in_cluster": 3200
        }
      }
    }
  }
}

  7. When a long-term solution is in place, we recommend you reset the cluster.max_shards_per_node.frozen limit.

    PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node.frozen": null
  }
}

::::::

::::::{tab-item} Self-managed Check the current status of the cluster according the shards capacity indicator:

GET _health_report/shards_capacity
{
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "yellow",
      "symptom": "Cluster is close to reaching the configured maximum number of shards for frozen nodes.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1000
        },
        "frozen": {
          "max_shards_in_cluster": 3000, <1>
          "current_used_shards": 2998 <2>
        }
      },
      "impacts": [
        ...
      ],
      "diagnosis": [
        ...
    }
  }
}
  1. Current value of the setting cluster.max_shards_per_node.frozen.
  2. Current number of open shards used by frozen nodes across the cluster.

Using the cluster settings API, update the cluster.max_shards_per_node.frozen setting:

PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node.frozen": 3200
  }
}

This increase should only be temporary. As a long-term solution, we recommend you add nodes to the oversharded data tier or reduce your cluster’s shard count on nodes that belong to the frozen tier. To verify that the change has fixed the issue, you can get the current status of the shards_capacity indicator by checking the data section of the health API:

GET _health_report/shards_capacity

The response will look like this:

{
  "cluster_name": "...",
  "indicators": {
    "shards_capacity": {
      "status": "green",
      "symptom": "The cluster has enough room to add new shards.",
      "details": {
        "data": {
          "max_shards_in_cluster": 1000
        },
        "frozen": {
          "max_shards_in_cluster": 3200
        }
      }
    }
  }
}

When a long-term solution is in place, we recommend you reset the cluster.max_shards_per_node.frozen limit.

PUT _cluster/settings
{
  "persistent" : {
    "cluster.max_shards_per_node.frozen": null
  }
}

::::::

::::::: ::::{tip} If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to . ::::