Shulou(Shulou.com)06/01 Report--

It is believed that many inexperienced people have no idea about how to modify the shards number in elasticsearch. Therefore, this paper summarizes the causes and solutions of the problem. Through this article, I hope you can solve this problem.

Problem found:

No log data display in kibana interface

ES, kibana, logstash, filebeat and other components are running normally

By looking at the log, we finally found a large number of errors in the log of logstash:

This action would add [2] total shards, but this cluster currently has [1000] / [1000] maximum shards open

After consulting the data on the Internet, it is found that the ES index is not enough (you can almost see it by roughly translating it).

It is said on the Internet that this problem is because there are only 1000 fragments by default above elasticsearch7, and there is no place to store and display newly collected logs beyond this number.

So you need to change the number of shards of ES

The methods are as follows:

Execute the following command on the host of ES:

Curl-XPUT-H "Content-Type:application/json"-d'{"persistent": {"cluster": {"max_shards_per_node": 10000}}''http://es-host:9200/_cluster/settings'

Refresh the kibana interface and start showing new logs

The problem is solved.

What's more frustrating is that when you search for solutions on the Internet, they are basically like this:

Xiaobai, as I thought, needed to modify the configuration file.

After reading the above, have you mastered the method of how to modify the shards number in elasticsearch? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.