Question 1: Elasticsearch startup report /usr/local/elasticsearch-6.2.2/logs/spring-boot.log (insufficient permissions)
Solution: 1. Switch to root user
2. Switch to the superior directory of elasticsearch-6.2.2,
Grammar for granting permissions : chown -R user: user elasticsearch-6.2.2/
chown -R es:es elasticsearch-6.2.2
Question 2: After enabling bootstrap.memory_lock: true, when the Elasticsearch cluster is started, the following error will be reported
ERROR : bootstrap checks failed memory locking requested for elasticsearch process but memory is not locked
Solution:
Solution 1: This solution is suitable for linux distributions that are not managed by systemd. Centos 6 and below can only be solved by this solution as a
temporary solution: ulimit -l Unlimited
permanent solution: edit /etc/security/limits.conf with root permissions and
add: * soft memlock unlimited
* hard memlock unlimited
Another: there is a pit here is that if there is a configuration file in the /etc/security/limits.d folder, it will overwrite the file you just modified, so please make sure that there are no other files in this directory. If there are any, please contact the operation and maintenance personnel to confirm the deletion
Use sysctl -p to take effect immediately.
Solution 2: Suitable for systemd-managed releases. An article mentioned that centos 7 needs to use this solution.
sudo vim /etc/systemd/system.conf
Add: DefaultLimitNOFILE=65536
DefaultLimitNPROC=32000
DefaultLimitMEMLOCK=infinity
Problem 3 ：ERROR: bootstrap checks failed
Solution:
vim /etc/security/limits.conf //Add, [valid after logout and re-login]
* soft nofile 300000
* hard nofile 300000
* soft nproc 102400
* hard nproc 102400
Question 4: system call filters failed to install; check the logs and fix your configuration or disable system call fil ters at your own risk
Solution:
1. vi ./elasticsearch-6.1.3/config/elasticsearch.yml
2. One Add under the column Memory: bootstrap.system_call_filter: false
Question 6: java.io.StreamCorruptedException: received HTTP response on transport port, ensure that transport port (not HTTP port) of a remote node is specified in the configuration
Solution: Check the cluster configuration in elasticsearch.yml, only configure the IP instead of port
Set data node:
increase: node.data:true