Yep! Believe so.... there is a changed cluster name in the yaml file, but that's commented out.
[root@es3:~] #grep cluster.name /etc/elasticsearch/elasticsearch.yml
#cluster.name: JF_cluster
So it should just be using the default cluster name of 'elasticsearch' in that case if I'm not mistaken.
These are the only contents of the elasticsearch log directory:
[root@es3:~] #ls -l /var/log/elasticsearch/
total 20
-rw-r--r--. 1 996 995 0 Jul 1 22:45 elasticsearch-access.log
-rw-r--r--. 1 996 995 0 Jul 1 22:45 elasticsearch_index_indexing_slowlog.log
-rw-r--r--. 1 996 995 0 Jul 1 22:45 elasticsearch_index_search_slowlog.log
-rw-r--r--. 1 996 995 18561 Jul 18 18:37 elasticsearch.log
So I guess, that's another problem I'll have to try and solve. In addition to why the cluster is still yellow at this point, I need to also figure out why node 3 isn't logging any activity, while clearly remaining a part of the cluster.
[root@logs:~] #curl localhost:9200/_cat/nodes?pretty=true
es3 66.147.235.108 14 35 0.04 d m JF_ES3
logs 216.120.248.98 6 37 0.65 d * JF_ES1
es2 66.147.235.153 12 33 0.00 d m JF_ES2
Sorry for the delay in responding, btw. I had to run out to the store.