[
https://issues.apache.org/jira/browse/SOLR-9371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15613339#comment-15613339
]
Jan Høydahl commented on SOLR-9371:
-----------------------------------
Hi, you can do something like this
{code}
bin/solr assert --not-started http://localhost:8983/solr/ --timeout 30000 -e
{code}
But it will only check if Solr is listening on the port, it will not check if
the process or PID file is gone, which I guess is what we need. I started on a
UtilsTool that will check PIDs and optionally kill, but that is not committed
yet. I'm fine with opening another JIRA for Windows and tackle it in next
release.
> Fix bin/solr script calculations - start/stop wait time and RMI_PORT
> --------------------------------------------------------------------
>
> Key: SOLR-9371
> URL: https://issues.apache.org/jira/browse/SOLR-9371
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 6.1
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Fix For: 6.2, master (7.0)
>
> Attachments: SOLR-9371.patch, SOLR-9371.patch
>
>
> The bin/solr script doesn't wait long enough for Solr to stop before it sends
> the KILL signal to the process. The start could use a longer wait too.
> Also, the RMI_PORT is calculated by simply prefixing the port number with a
> "1" instead of adding 10000. If the solr port has five digits, then the rmi
> port will be invalid, because it will be greater than 65535.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
