[
https://issues.apache.org/jira/browse/SOLR-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17708037#comment-17708037
]
Houston Putman commented on SOLR-15948:
---------------------------------------
I actually ran into this a lot when doing integration tests for the solr
operator.
An easy way to reproduce this is using the docker image. Try to run it using a
small amount of memory/CPU, it will likely take quite a bit of time to start
(maybe over 30 seconds).
Then try to run solr stop within the docker image
{{docker run -it --rm -m 512m --cpus=".2" --name=solr-test solr:9.2 -c}}
Then separately a few seconds later:
{{docker exec solr-test solr stop -p 8983}}
It doesn't relate to the issue 100% but it's kind of the same. Solr stop relies
on the server coming up 100%.
> Server can't be stopped if there are startup errors
> ---------------------------------------------------
>
> Key: SOLR-15948
> URL: https://issues.apache.org/jira/browse/SOLR-15948
> Project: Solr
> Issue Type: Bug
> Affects Versions: 9.0
> Reporter: Ishan Chattopadhyaya
> Priority: Major
>
> If there are startup errors during
> {code}
> bin/solr -c
> {code}
> then a subsequent
> {code}
> bin/solr stop
> {code}
> doesn't work and times out.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
