[
https://issues.apache.org/jira/browse/SOLR-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477773#comment-16477773
]
Shawn Heisey commented on SOLR-6734:
------------------------------------
I am imagining a VERY slim process, with dependencies as minimal as possible.
If it's Java, which I see as likely, then it should be able to run with a very
small heap. Logging could be done with stdout, but we might want to have it
use slf4 since those jars are already present. I see the primary job of the
agent as configuring/starting/stopping the main Solr process, as you mentioned.
We can think about other capabilities as the project evolves.
With effective and cross-platform inter-process communication (IPC), the agent
wouldn't need any kind of direct user interaction, which would keep its
footprint small. All user interaction for the agent could be handled by
SolrCLI and Solr itself (which are already set up to handle user input),
sending messages to the agent. It looks like Java has a socket implementation
that's not difficult to use.
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
