Checking shards creation

When a node hits cluster.max_shards_per_node limit, the cluster status remains green.

Logs from elasticsearch:

    "Caused by: org.elasticsearch.common.ValidationException: Validation Failed: 1: this action would add [###] total shards, but this cluster currently has [1000]/[1000] maximum shards open;",

Cluster health:

    {
  "cluster_name" : "###",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : ###,
  "number_of_data_nodes" : ###,
  "active_primary_shards" : 1001,
  "active_shards" : 1001,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0
}

And even if you run the test through filebeat (filebeat test output), it will pass successfully, because the shard creation is not checked.

Has anyone solved the problem of checking the write to elastic? Checking the connection turns out to be insufficient and it does not mean that the elastic can receive new shards.

Welcome to our community! :smiley:

That's a valid point, it'd be worth raising an issue on https://github.com/elastic/beats/issues to see if that's something that we can check for as part of those startup checks.

That said, it's always good to fix the underlying issue here and look at the high shard count.