[
https://issues.apache.org/jira/browse/SOLR-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley closed SOLR-6126.
------------------------------
Resolution: Not a Problem
Oooh, ok. I guess since in this mode of operation no documents are sent to any
replica, all that needs to be done is to merge additional segments on each
replica (leader or not is irrelevant). Interestingly, this GoLive script looks
fairly generic. It's nothing more than a distributed addIndexes() call
followed by a distributed commit. There's nothing Hadoop/HDFS oriented about
it, even if it's only used in such contexts.
> MapReduce's GoLive script should support replicas
> -------------------------------------------------
>
> Key: SOLR-6126
> URL: https://issues.apache.org/jira/browse/SOLR-6126
> Project: Solr
> Issue Type: Improvement
> Components: contrib - MapReduce
> Reporter: David Smiley
>
> The GoLive feature of the MapReduce contrib module is pretty cool. But a
> comment in there indicates that it doesn't support replicas. Every
> production SolrCloud setup I've seen has had replicas!
> I wonder what is needed to support this. For GoLive to work, it assumes a
> shared file system (be it HDFS or whatever, like a SAN). If perhaps the
> replicas in such a system read from the very same network disk location, then
> all we'd need to do is send a commit() to replicas; right?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
