ElasticSearch 5.0.0 installation and deployment common errors or problems

ElasticSearch 5.0.0 installation and deployment common errors or problems

 

Question one:

 
[2016-11-06T16:27:21,712][WARN ][o.e.b.JNANatives ] unable to install syscall filter:
 
Java.lang.UnsupportedOperationException: seccomp unavailable: requires kernel 3.5+ with CONFIG_SECCOMPandCONFIG_SECCOMP_FILTERcompiledinatorg.elasticsearch.bootstrap.Seccomp.linuxImpl(Seccomp.java:349) ~[elasticsearch-5.0.0.jar:5.0.0]
 
at org.elasticsearch.bootstrap.Seccomp.init(Seccomp.java:630) ~[elasticsearch-5.0.0.jar:5.0.0]
 
Reason: A series of errors are reported, you don't need to panic, it is actually just a warning, mainly because your Linux version is too low.
 
solution:
1. Reinstall the new version of the Linux system
2. The warning does not affect the use and can be ignored
 
Question two:
ERROR: bootstrap checks failed
 
max file descriptors [4096] for elasticsearch process likely too low, increase to at least [65536]
 
Reason: Unable to create a local file problem, the maximum number of files a user can create is too small
 
solution:
Switch to the root user, edit the limits.conf configuration file, and add something like the following:
 
vi /etc/security/limits.conf
 
Add the following:
* soft nofile 65536
 
* hard nofile 131072
 
* soft nproc 2048
 
* hard nproc 4096
Note: * represents all user names in Linux (such as hadoop)
 
Save, log out, and log in again to take effect
 
Question three:
max number of threads [1024] for user [es] likely too low, increase to at least [2048]
Reason: Unable to create local thread problem, the maximum number of threads the user can create is too small
Solution: Switch to the root user, enter the limits.d directory, and modify the 90-nproc.conf configuration file.
 
vi /etc/security/limits.d/90-nproc.conf
 
Find the following:
 
* soft nproc 1024
 
#change into
 
* soft nproc 2048
 
Question four:
max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
Reason: The maximum virtual memory is too small
Solution: Switch to the root user and modify the configuration file sysctl.conf
 
vi /etc/sysctl.conf
 
Add the following configuration:
 
vm.max_map_count=655360
 
and execute the command:
 
sysctl -p
 
Then restart elasticsearch to start successfully.
 
Question five:
ElasticSearch startup cannot find host or route
Reason: Problem with ElasticSearch unicast configuration
solution:
Check the configuration file in ElasticSearch
vi config / elasticsearch.yml
Find the following configuration:
 
discovery.zen.ping.unicast.hosts:["192.168.**.**:9300","192.168.**.**:9300"]
In general, there is a problem with the configuration here, pay attention to the writing format
 
Question six:
org.elasticsearch.transport.RemoteTransportException: Failed to deserialize exception response from stream
 
Reason: Inconsistent jdk versions between ElasticSearch nodes
 
Solution: ElasticSearch cluster unified jdk environment
 
Question seven:
Unsupported major.minor version 52.0
 
Reason: jdk version problem is too low
Solution: Change the jdk version, ElasticSearch5.0.0 supports jdk1.8.0
 
Question eight:
bin/elasticsearch-plugin install license
ERROR: Unknown plugin license
 
Reason: The plugin command has changed since ElasticSearch 5.0.0
Solution: Install all plugins using latest command

 

bin/elasticsearch-plugin install x-pack

Guess you like

Origin http://43.154.161.224:23101/article/api/json?id=326450185&siteId=291194637