lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] [Commented] (SOLR-6734) Standalone solr as *two* applications -- Solr and a controlling agent
Date Wed, 16 May 2018 17:26:00 GMT


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:
>             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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message