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

This article mainly introduces "what should be paid attention to when building ElasticSearch7". In daily operation, I believe that many people have doubts about what problems they should pay attention to when building ElasticSearch7. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts of "what should you pay attention to when building ElasticSearch7?" Next, please follow the editor to study!

The 1.Jdk version must be the same.

two。 Clearly set which node is the master node and which node is the data node node.master attribute (the master node attribute is set to true, the data node is set to false, of course, the master node can also store data)

3.pack.ml.enabled: false

If you do not need to use the machine learning feature, you can set it to disable in elasticsearch.yml:

4. Exception org.elasticsearch.transport.RemoteTransportException: Failed to deserialize exception response from stream

Reason: inconsistent jdk versions between ElasticSearch nodes

5. Exception org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: join validation on cluster state with a different cluster uuid DGeDa4wNQ7OnyZyxWJRS_w than local cluster uuid u5-SNBcDR3mQHj0Vm-whVQ, rejecting

Because two independent clusters cannot join a cluster, you should delete the corresponding data data (that is, the data in the corresponding data and logs in the yml, restart the service)

6. Exception [node-2] master not discovered yet: have discovered [{node-1}]

Reason: to initialize master, in the yml configuration file of E, the following:

Cluster.initial_master_nodes: ["192.168.1.3"]

7. Exception Unsupported major.minor version 52.0

Reason: jdk version is too low

8. Exception bin/elasticsearch-plugin install license ERROR: Unknown plugin license

Reason: plug-in commands have changed since ElasticSearch6.0.0

Solution: bin/elasticsearch-plugin install x-pack

9. Startup exception: ERROR: bootstrap checks failed system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk

Reason: because Centos6 does not support SecComp, and the default bootstrap.system_call_filter of ES5.2.1 is true for detection, it causes the detection to fail. After the failure, ES cannot be started directly. For details, see: https://github.com/elastic/elasticsearch/issues/22899

Solution: configure bootstrap.system_call_filter as false in elasticsearch.yml, and note that it should be under Memory

Bootstrap.memory_lock: false

Bootstrap.system_call_filter: false

At this point, the study of "what to pay attention to when building ElasticSearch7" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.