Elastic search storage exception

Elasticsearch run in read only mode due to storage. i dont want to extend storage this time because it is only for testing purpose.

below is Elasticsearch yml file

# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
#       Before you set out to tweak and tune the configuration, make sure you
#       understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
cluster.name: my-application
cluster.routing.allocation.disk.threshold_enabled: false
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
#node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1

#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# By default Elasticsearch is only accessible on localhost. Set a different
# address here to expose this node on the network:
#
#network.host: 192.168.0.1
#
# By default Elasticsearch listens for HTTP traffic on the first free port it
# finds starting at 9200. Set a specific HTTP port here:
#
http.port: 9200
#
# For more information, consult the network module documentation.
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when this node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
#discovery.seed_hosts: ["host1", "host2"]
#
# Bootstrap the cluster using an initial set of master-eligible nodes:
#
#cluster.initial_master_nodes: ["node-1", "node-2"]
#
# For more information, consult the discovery and cluster formation module documentation.
#
# ---------------------------------- Various -----------------------------------
#
# Require explicit names when deleting indices:
#
#action.destructive_requires_name: true

Which version of Elasticsearch you are running on?

If your version is 7.4 onwards then you should be just fine after you delete some data or indices in your cluster to bring down the disk usage.

What exactly are you looking for here then?

simply i want to run elastic in limited storage that i have free in my disk 10gb. is there any way elastic does not read storage capacity or ignore storage requirement of 50GB.

Look at Cluster-level shard allocation and routing settings | Elasticsearch Guide [7.15] | Elastic

You can set on a cluster level: cluster.routing.allocation.disk.threshold_enabled to false (at your own risk) or set the other related settings.

Already add this command to false. please look into above added yml file. but still it is not working.

What are the logs?

@dadoonet thanks mr i was found the solution.

first i add below line in elastic yml file memory section

cluster.routing.allocation.disk.threshold_enabled: false

secondly i face kibana server not ready yet then i run below command

curl --request DELETE “http://localhost:9200/.kibana*”

@benettonb1 already solved

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.