[
https://issues.apache.org/jira/browse/SOLR-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209174#comment-14209174
]
Shawn Heisey commented on SOLR-6734:
------------------------------------
Some additional detail I thought of for this idea:
* The agent could listen on a TCP port for connections from agents running on
other servers.
** This would be primarily for SolrCloud, but there might be non-cloud uses
too. This would enable stopping and starting of Solr instances across an
entire cluster.
** Not entirely sure about how to configure an entire cluster of agents ...
perhaps like zookeeper, where all servers contain the entire list of host:port
pairs. A centralized config in Zookeeper would not be a bad idea either, as
long as we have some way of altering or resetting that config.
** A shared authentication key and a cluster name in the config would be a
good idea. The info in an incoming request would need to validate against
both, and perhaps even against the host:port list. This data might also be
used for TLS.
* The heap set by the script that starts the agent would be very small. Even
with hundreds of servers in the config, I would imagine that the memory
requirements would be minimal.
* Most startup options for Solr would be configurable and used by the agent
when starting Solr. Thinking about a cluster, we probably would want to have a
common set of options as well as per-server options that can supplement or
override common options.
* We might even be able to control standalone zookeeper processes with this
agent.
> Standalone solr as *two* applications -- Solr and a controlling agent
> ---------------------------------------------------------------------
>
> Key: SOLR-6734
> URL: https://issues.apache.org/jira/browse/SOLR-6734
> Project: Solr
> Issue Type: Sub-task
> Reporter: Shawn Heisey
>
> In a message to the dev list outlining reasons to switch from a webapp to a
> standalone app, Mark Miller included the idea of making Solr into two
> applications, rather than just one. There would be Solr itself, and an agent
> to control Solr.
> http://mail-archives.apache.org/mod_mbox/lucene-dev/201305.mbox/%3C807476C6-E4C3-4E7E-9F67-2BECB63990DE%40gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
