Cluster.max_shards_per_node

monitoring

#1

I see following message through Dev Tools in Kibana:

#! Deprecation: In a future major version, this request will fail because this action would add [10] total shards, but this cluster currently has [9556]/[5000] maximum shards open. Before upgrading, reduce the number of shards in your cluster or adjust the cluster setting [cluster.max_shards_per_node].

yet via Monitoring data node has about 2000.

Please advise.


(Mark Walkom) #2

What is the output from the _cat/health?v API?


#3
epoch      timestamp cluster status node.total node.data shards  pri relo init unassign pending_tasks max_task_wait_time active_shards_percent
1542600474 04:07:54  x green          x         5   9612 4805    0    0        0             0                  -                100.0%

(Mark Walkom) #4

Ok, then as it's suggesting you need to reduce your shard count.

What is the output from _cat/indices?v.


(Christian Dahlqvist) #5

That is indeed a new warning that you have far too many shards for a cluster that size. Please read this blog post on shards and siding practices and work to reduce that significantly.


(system) #6

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