[
https://issues.apache.org/jira/browse/SOLR-14442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111935#comment-17111935
]
Christine Poerschke commented on SOLR-14442:
--------------------------------------------
Thanks [~mkhl] for taking a look at {{solr.cmd}} here!
bq. ... it seems that current code doesn't stop process ...
Wow, that's an interesting and unexpected side effect find.
In terms of a {{solr/CHANGES.txt}} entry for this ticket I'd been undecided and
wondered if it could be omitted perhaps, jstack being implementation detail to
an extent and also not something the typical user would be likely to see,
hopefully. A fix for {{solr.cmd}} not stopping as expected might change that
though, thoughts?
> bin/solr to attempt jstack before killing hung Solr instance
> ------------------------------------------------------------
>
> Key: SOLR-14442
> URL: https://issues.apache.org/jira/browse/SOLR-14442
> Project: Solr
> Issue Type: Improvement
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-14442.patch, SOLR-14442.patch, SOLR-14442.patch,
> screenshot-1.png
>
>
> If a Solr instance did not respond to the 'stop' command in a timely manner
> then the {{bin/solr}} script will attempt to forcefully kill it:
> [https://github.com/apache/lucene-solr/blob/releases/lucene-solr/8.5.1/solr/bin/solr#L859]
> Gathering of information (e.g. a jstack of the java process) before the kill
> command may be helpful in determining why the instance did not stop as
> expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
