[
https://issues.apache.org/jira/browse/SOLR-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477522#comment-16477522
]
Jan Høydahl commented on SOLR-6734:
-----------------------------------
I think the original issue and email thread is very old, and mostly talking
about things that have already been solved or will be solved if we replace
start.jar with solr-start.jar and take control over more ourselves.
But are you envisioning the agent as a super slim process which is what is
really being started with {{bin/solr start}}, and then its only task is to
spawn the main Solr JVM with correct settings, and receive agent commands
(REST?) for restart, reconfiguring etc? Or do you think it should be a fatter
agent process which users need to relate to in terms of separate commands to
start, stop, configure etc? It is the latter situation I'd like to avoid by
keeping Solr as one process.
> 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: [email protected]
For additional commands, e-mail: [email protected]
