You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "David Eric Pugh (Jira)" <ji...@apache.org> on 2020/11/21 11:30:00 UTC
[jira] [Created] (SOLR-15010) Missing jstack warning is alarming,
when using bin/solr as client interface to solr
David Eric Pugh created SOLR-15010:
--------------------------------------
Summary: Missing jstack warning is alarming, when using bin/solr as client interface to solr
Key: SOLR-15010
URL: https://issues.apache.org/jira/browse/SOLR-15010
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 8.7
Reporter: David Eric Pugh
In SOLR-14442 we added a warning if jstack wasn't found. I notice that I use the bin/solr command a lot as a client, so bin solr zk or bin solr healthcheck.
For example:
{{docker exec solr1 solr zk cp /security.json zk:security.json -z zoo1:2181}}
All of these emit the message:
The currently defined JAVA_HOME (/usr/local/openjdk-11) refers to a location
where java was found but jstack was not found. Continuing.
This is somewhat alarming, and then becomes annoying. Thoughts on maybe only conducting this check if you are running {{bin/solr start}} or one of the other commands that is actually starting Solr as a process?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org