[
https://issues.apache.org/jira/browse/SOLR-15469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874180#comment-17874180
]
Eric Pugh edited comment on SOLR-15469 at 8/16/24 10:37 AM:
------------------------------------------------------------
This use case has become less frequent in a time of Docker, Kubernets etc...
I'd also recommend that if you are going for clustering and robustness, well we
want to make it even easier to run Solr in a cluster (cloud) mode so that is
the way you get your fail over etc.
was (Author: epugh):
This use case has become less frequent in a time of Docker etc... We're also
working on making Solr more robust and cloud friendly so you could host many
indexes in a single solr process...
> start/stop script fails on multiple instance
> --------------------------------------------
>
> Key: SOLR-15469
> URL: https://issues.apache.org/jira/browse/SOLR-15469
> Project: Solr
> Issue Type: Bug
> Components: scripts and tools, SolrCLI
> Reporter: Danilo
> Priority: Minor
> Labels: cluster, instances, pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> When more instances of solr run on the same machine. The bash script solr
> fail to get correct pid of process. This cause problems to get status
> information or when stop/restart solr instance.
> In optical to use solr like a cluster service this is essential for the
> cluster to know the healt of service.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
