The symlink thing sounds... complicated, but as you say you're going
another route....
The indexing speed you're seeing is surprisingly slow, I'd get to the root
of the timeouts before giving up. SolrCloud simply _can't_ be that slow
by design, something about your setup is causing that I suspect. The
timeouts you're seeing are certainly a clue here. Incoming updates have
a couple of things happen
1> the incoming request is pulled apart. Any docs for this shard are
indexed and forwarded to any replicas.
2> any docs that are for a different shard are packed up and forwarded
to the leader for that shard. Which in turn distributes them to any
replicas.
So I _suspect_ that indexing will be a bit slower, there's some additional
communication going on. But not _that_ much slower. Any clue what your
slow server is doing that would cause it to timeout?
Best
Erick
On Mon, Jul 9, 2012 at 4:11 PM, avenka <ave...@gmail.com> wrote:
> Hmm, never mind my question about replicating using symlinks. Given that
> replication on a single machine improves throughput, I should be able to get
> a similar improvement by simply sharding on a single machine. As also
> observed at
>
> http://carsabi.com/car-news/2012/03/23/optimizing-solr-7x-your-search-speed/
>
> I am now benchmarking my workload to compare replication vs. sharding
> performance on a single machine.
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-replication-question-tp3993761p3994017.html
> Sent from the Solr - User mailing list archive at Nabble.com.
