Pattern selector

Most relevant patterns first. Most helpful ones displayed. Click here to show all.

  1. Elasticsearch.main() has thrown a RuntimeException
    Elasticsearch Core
    4
    8
    0
  2. Elasticsearch.init() has thrown a RuntimeException
    Elasticsearch Core
    4
    10
    0

Your stack trace compared to the selected pattern

Jump to solutionsExpand frames
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 max file descriptors [4096] for elasticsearch process likely too low, increase to at least [65536] please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
12 matching frames hidden
    at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:70)
    at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:63)

External results for this pattern (10)

  1. czeraszvia GitHub3 months 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 max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
    Show stack trace
  2. bootstrap checks failed max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
    Show stack trace
  3. danmvia GitHub4 months 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
    Show stack trace
  4. djschnyvia GitHub4 months 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
    Show stack trace
  5. naisanzavia GitHub4 months 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 max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
    Show stack trace
  6. 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 max file descriptors [4096] for elasticsearch process likely too low, increase to at least [65536] please set [discovery.zen.minimum_master_nodes] to a majority of the number of master eligible nodes in your cluster max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
    Show stack trace
  7. fxpvia Stack Overflow4 months 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
    Show stack trace
  8. gboorvia GitHub7 months ago
    bootstrap checks failed search_1 | max virtual memory areas vm.max_map_count [65530] likely too low, increase to at least [262144]
    Show stack trace
  9. bootstrap checks failed max number of threads [1024] for user [elasticsearch] likely too low, increase to at least [2048]
    Show stack trace
  10. f3rdyvia GitHub2 years 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
    Show stack trace