We are using ELK for logging (of course) but when we don't use the server for several weeks and we start it up again in the browser it takes a very long time before it shows some info. We have it also that it doesn't show anything but a red bar on top that it failed.
Is there a way (crontab?) to do the indexing automatically? So when we start it up again it doesn't need to index it all again?
What version of Kibana and Elasticsearch are you running? Any errors either in Kibana or ES when you see the red bar error? Kibana doesn't index data, Elasticsearch does, so i'm not sure what you're referring to when asking about automated indexing.
I have changed the HEAP_SIZE (which was 1g) to the half of the memory what the server has. All has been fixed now.
What i did on a Ubuntu 14.04
/etc/security/limits.conf:
elasticsearch - nofile 65535
elasticsearch - memlock unlimited
/etc/default/elasticsearch (on CentOS/RH: /etc/sysconfig/elasticsearch ):
ES_HEAP_SIZE=4g
MAX_OPEN_FILES=65535
MAX_LOCKED_MEMORY=unlimited
/etc/elasticsearch/elasticsearch.yml:
bootstrap.mlockall: true
Rebooted the server and Elasticsearch started the command with -Xms4g -Xmx4g
And yes sorry, this had nothing to do with Kibana after all. But because i was pointing my browser to Kibana i thought it got stuck.
Cool, thanks for the update!
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.