Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via GitHub by jasontedor
, 1 year ago
bootstrap checks failed initial heap size [268435456] not equal to maximum heap size [2147483648]; this can cause resize pauses and prevents mlockall from locking the entire heap please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster
via GitHub by ajaybhatnagar
, 1 year ago
bootstrap checks failed max file descriptors [65535] for elasticsearch process likely too low, increase to at least [65536]
via GitHub by jasontedor
, 2 years ago
please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster.
via GitHub by tianon
, 2 years ago
please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster.
via GitHub by tianon
, 1 year ago
please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster.
via GitHub by djschny
, 2 years ago
please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster.
java.lang.RuntimeException: bootstrap checks failed
initial heap size [268435456] not equal to maximum heap size [2147483648]; this can cause resize pauses and prevents mlockall from locking the entire heap
please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster	at org.elasticsearch.bootstrap.BootstrapCheck.check(BootstrapCheck.java:134)