we recently started looking into deploying multiple instances of logstash on the same box and noticed that when the logstash settings directory is changed from the default (/etc/logstash), the jvm.options file is no longer read.
For example in our current setup we have:
/etc/logstash/instance1/(logstash.yml, jvm.options etc)
/etc/logstash/instance2/(logstash.yml, jvm.options etc)
and jvm.options is not detected.
If we move jvm.options back in /etc/logstash/ then it's read as normale (although neither instance has /etc/logstash/ has settings dir)
Looking into the bin/logstash.lib.sh I found a snippet of code where the /etc/logstash/jvm.options path is hardcoded:
if [ -z "$LS_JVM_OPTS" ]; then
for jvm_options in /etc/logstash/jvm.options
Is this a design decision (as the idea is it doesn't make sense to have a separate jvm.options for each installation running on the same box) or is it a bug?
Any help is appreciated