In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.The Elasticsearch Check-Up is free and requires no installation.
In addition to reading about the misuse of wildcards in Elasticsearch, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.
The Elasticsearch Check-Up is free and requires no installation.
Run the Elasticsearch check-up to receive recommendations like this:
Run Check-Up
The following configuration error was detected on node 123...
Description
This error can have a severe impact on your system. It's important to understand that it was caused by...
Recommendation
In order to resolve this issue and prevent it from occurring again, we recommend that you begin by changing the configuration to...
X-PUT curl -H "Content-Type: application/json" [customized recommendation]
Overview
It is possible to reduce the risk of accidental deletion of indices by preventing the use of wildcard for destructive (deletion) operations.
How to fix the issue
To check whether this setting exists on the cluster, run:
GET /_cluster/settings/action*
Look for a setting called:
action.destructive_requires_name
To apply this setting use:
PUT /_cluster/settings
{
"transient": {
"action.destructive_requires_name":true
}
}To remove this setting use:
PUT /_cluster/settings
{
"transient": {
"action.destructive_requires_name":false
}
}Note that this setting can also be applied on each node via the elasticsearch.yml file, but the cluster setting will take priority over any individual node settings.
