You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ramkumar Aiyengar (JIRA)" <ji...@apache.org> on 2014/11/12 00:45:34 UTC
[jira] [Commented] (SOLR-6731) Add a way to run/enable a plugin
per-shard
[ https://issues.apache.org/jira/browse/SOLR-6731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207350#comment-14207350 ]
Ramkumar Aiyengar commented on SOLR-6731:
-----------------------------------------
We already expose a fairly reusable mechanism to hold a leadership election. What does this buy us on top of the plugin using this to decide whether it should do anything?
> Add a way to run/enable a plugin per-shard
> ------------------------------------------
>
> Key: SOLR-6731
> URL: https://issues.apache.org/jira/browse/SOLR-6731
> Project: Solr
> Issue Type: Improvement
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
>
> There should be a way to run/enable a Solr plugin per-shard. An example of such a plugin could be the couchbase indexer which is added as a couch replica and then data is pushed to such a plugin by couchdb automatically. We wouldn't want all the replicas in Solr to start such a plugin automatically. Even if we enable/disable the plugin via an API, we would still want automatic failover if the node running the plugin went down.
--
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