[
https://issues.apache.org/jira/browse/SOLR-9714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16105273#comment-16105273
]
Christine Poerschke commented on SOLR-9714:
-------------------------------------------
bq. ... Another related issue is that if you try to stop Solr with an incorrect
STOP_PORT or an incorrect STOP_KEY ... then the controlled stop through stop
port/key fails, but then the process is still forcefully killed after some
seconds. Should we not instead exit with message "invalid stop port/key given".
...
Along similar lines, I was wondering about support for generally opting out of
forceful kills e.g. once the SOLR_STOP_WAIT time is up, perhaps one would wish
to investigate (e.g. _jstack_ the process) why the process did not exit
(assuming stop port and key were correct) in a timely manner.
> Ability to configure STOP_PORT
> ------------------------------
>
> Key: SOLR-9714
> URL: https://issues.apache.org/jira/browse/SOLR-9714
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools, SolrCloud
> Affects Versions: 5.5.3, 6.2.1
> Reporter: hu xiaodong
> Priority: Minor
> Attachments: SOLR-9714.patch, SOLR-9714.patch
>
>
> Our system just has port planning,we have the requirement to configure what
> to use as stop port explicitly. but now I can configure the stop_port on the
> starting script($SOLR_HOME/bin/solr), but can not use the port to stop solr
> gracefully. I think the script has a little problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
