I am using OSS version of Elasticsearch, so I have just downloaded the zip file, unzipped it, created the required folders and start the service from bin folder.
Yes, There were logs initially and then it suddenly stopped adding new logs. I restarted Elasticsearch services a few times and every time it was generating logs for few hours and stops again adding new logs.
Why are you setting all the so small, those are incredibly small numbers for disk usage? , plus they are in the wrong order low should be the lowest setting not higher than high and flood_stage.
Also question when the logs stop is elasticsearch still running? Can you still
curl http://localhost:9200
and get a result?
Are you running out of disk space in general?
6.3.1 Is a very old release, but that should not be the issue.
For the QA, I have set with lower numbers. but for the production, I have higher numbers. Thanks for noting the order, I'll correct it.
Yes, Elasticsearch service is running fine. Elasticsearch was doing index, search, etc. operation perfectly fine. It's just the new logs are not being added to the log files.
What log level do you have set?
How are looking at the logs?... they do rotate...
Are you looking at the new log file after it rotates?
Perhaps a misconfiguration in the log rotations settings?
Also elastic does not print a lot of logs when things are just static... so are you sure you are actually not getting logs?
Apologies but I can not debug the whole logging set up. What I would perhaps suggest is go back to the default log4j2.properties see if that works as expected and then proceed to adjust from there.
I already noticed you hard coded the Cluster name instead of
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.