elasticsearch/docs/reference/tab-widgets/troubleshooting/data/enable-cluster-allocation.asciidoc
2022-07-27 14:31:06 +02:00

127 lines
3.5 KiB
Text

// tag::cloud[]
In order to get the shards assigned we'll need to change the value of the
<<cluster-routing-allocation-enable, configuration>> 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-get-settings, cluster setting>> and changing the configured value to
`all`.
**Use {kib}**
//tag::kibana-api-ex[]
. Log in to the {ess-console}[{ecloud} console].
+
. On the **Elasticsearch Service** 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 https://support.elastic.co[Elastic Support].
If your deployment doesn't include {kib}, all you need to do is
{cloud}/ec-access-kibana.html[enable it first].
. Open your deployment's side navigation menu (placed under the Elastic logo in the upper left corner)
and go to **Dev Tools > Console**.
+
[role="screenshot"]
image::images/kibana-console.png[{kib} Console,align="center"]
. Inspect the `cluster.routing.allocation.enable` <<cluster-get-settings, cluster setting>>:
+
[source,console]
----
GET /_cluster/settings?flat_settings
----
+
The response will look like this:
+
[source,console-result]
----
{
"persistent": {
"cluster.routing.allocation.enable": "none" <1>
},
"transient": {}
}
----
// TESTRESPONSE[skip:the result is for illustrating purposes only as don't want to change a cluster-wide setting]
+
<1> Represents the current configured value that controls if data is partially
or fully allowed to be allocated in the system.
. <<cluster-update-settings,Change>> the <<cluster-routing-allocation-enable, configuration>>
value to allow all the data in the system to be fully allocated:
+
[source,console]
----
PUT _cluster/settings
{
"persistent" : {
"cluster.routing.allocation.enable" : "all" <1>
}
}
----
// TEST[continued]
+
<1> The new value for the `allocation.enable` system-wide configuration
is changed to allow all the shards to be allocated.
//end::kibana-api-ex[]
// end::cloud[]
// tag::self-managed[]
In order to get the shards assigned we'll need to change the value of the
<<cluster-routing-allocation-enable, configuration>> 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-get-settings, cluster setting>> and changing the configured value to
`all`.
. Inspect the `cluster.routing.allocation.enable` <<cluster-get-settings, cluster setting>>:
+
[source,console]
----
GET /_cluster/settings?flat_settings
----
+
The response will look like this:
+
[source,console-result]
----
{
"persistent": {
"cluster.routing.allocation.enable": "none" <1>
},
"transient": {}
}
----
// TESTRESPONSE[skip:the result is for illustrating purposes only as don't want to change a cluster-wide setting]
+
<1> Represents the current configured value that controls if data is partially
or fully allowed to be allocated in the system.
. <<cluster-update-settings,Change>> the <<cluster-routing-allocation-enable, configuration>>
value to allow all the data in the system to be fully allocated:
+
[source,console]
----
PUT _cluster/settings
{
"persistent" : {
"cluster.routing.allocation.enable" : "all" <1>
}
}
----
// TEST[continued]
+
<1> The new value for the `allocation.enable` system-wide configuration
is changed to allow all the shards to be allocated.
// end::self-managed[]