[jira] [Commented] (SOLR-15010) Missing jstack warning is alarming, when using bin/solr as client interface to solr

["David Eric Pugh (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-15010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261628#comment-17261628 ] 

David Eric Pugh commented on SOLR-15010:
----------------------------------------

[~janhoy][~cpoerschke] I've pushed up a PR for this, I'd love your review.  Shell hacking makes me nervous ;-)

> 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
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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