[
https://issues.apache.org/jira/browse/SOLR-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16478313#comment-16478313
]
Shawn Heisey commented on SOLR-6734:
------------------------------------
Further thought: The agent wouldn't need to be responsible for making config
changes. It's probably better to have that handled in SolrCLI/Solr, for two
reasons that come to mind immediately: 1) The user interface for these things
would be there, not in the agent. 2) So the number of dependencies the agent
requires can be as small as possible. I'd be willing to bet that the main Solr
app already has all the dependencies we are likely to want for creating and
manipulating config files.
I do think it might be a good idea to have some limited monitoring capability
in the agent. If the agent detects that the Solr process has died or isn't
responsive on one of the /admin/system API calls that should complete quickly
(after working correctly for a certain amount of time after startup), it would
be fairly easy to have it send an alarm email, if the user configures that.
The jar for that capability is only 213KB.
https://mvnrepository.com/artifact/javax.mail/javax.mail-api/1.6.1
> 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
