problem 1: ELK version must be unified

when installing ELK, the version number must be the same, for example, the version number is “5.6.12”, then:

• Elasticsearch version number must be: 5.6.12
• Logstash must be: 5.6.12
• Kibana version number must be: 5.6.12
• ik word divider version number must be: 5.6.12

problem 2: spring-boot-starter-data-elasticsearch corresponds to es version inconsistency, resulting in an error

this problem is a problem that breaks programmers. When your ELK is installed and SpringBoot integrates ES cluster, it will add spring-boot-starter-data-elasticsearch. We must think that the version number of this plug-in has nothing to do with the version number of ES. A lot to do, they have a version number of the corresponding relationship between the original and the diagram below (picture from official: https://docs.spring.io/spring-data/elasticsearch/docs/current/reference/html/#new-features) :

So friends, if you do ES cluster function, remember to set up according to the SpringBoot version number, do not wait for the installation of ELK, only to find that the SpringBoot version number does not correspond, which will cost a lot of time (because ELK is not easy to install).

other issues will continue to update…