You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2014/11/14 06:02:34 UTC
[jira] [Comment Edited] (SOLR-6734) Standalone solr as *two*
applications -- Solr and a controlling agent
[ https://issues.apache.org/jira/browse/SOLR-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14211832#comment-14211832 ]
Shawn Heisey edited comment on SOLR-6734 at 11/14/14 5:02 AM:
--------------------------------------------------------------
I thought of an alternative to the TCP port for agent communication -- a work queue in zookeeper like the SolrCloud overseer. A separate queue for each agent might be cleaner, but I don't know what the performance implications would be when scaling to a large number of servers.
I haven't worked through all the scenarios in my mind ... but if agent communication is something that we need when not in cloud mode, then zookeeper might not be the right path.
was (Author: elyograg):
I thought of an alternative to the TCP port for agent communication -- a work queue in zookeeper like the SolrCloud overseer. A separate queue for each agent might be cleaner, but I don't know what the performance implications would be when scaling to a large number of servers.
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org