bq: I thought SolrCloud replicas were replication, and you imply parallel
indexing
Absolutely! You couldn't get near-real-time indexing if you relied on
replication a-la
3x. And you also couldn't guarantee consistency.
Say you have 1 shard, a leader and a follower (i.e. 2 replicas). Now you
thro
@Erick,
Problem space is not constant indexing. I thought SolrCloud replicas were
replication, and you imply parallel indexing. Good to know.
On Sunday, January 25, 2015, Erick Erickson wrote:
> @Shawn: Cool table, thanks!
>
> @Dan:
> Just to throw a different spin on it, if you migrate to S
Thanks!
On Sunday, January 25, 2015, Erick Erickson wrote:
> @Shawn: Cool table, thanks!
>
> @Dan:
> Just to throw a different spin on it, if you migrate to SolrCloud, then
> this question becomes moot as the raw documents are sent to each of the
> replicas so you very rarely have to copy the fu
@Shawn: Cool table, thanks!
@Dan:
Just to throw a different spin on it, if you migrate to SolrCloud, then
this question becomes moot as the raw documents are sent to each of the
replicas so you very rarely have to copy the full index. Kind of a tradeoff
between constant load because you're sending
On 1/24/2015 10:56 PM, Dan Davis wrote:
> When I polled the various projects already using Solr at my organization, I
> was greatly surprised that none of them were using Solr replication,
> because they had talked about "replicating" the data.
>
> But we are not Pinterest, and do not expect to be
When I polled the various projects already using Solr at my organization, I
was greatly surprised that none of them were using Solr replication,
because they had talked about "replicating" the data.
But we are not Pinterest, and do not expect to be taking in changes one
post at a time (at least th
