+1 for CloudSolrServer
CloudSolrServer also has built in fault tolerance (i.e. if the master shard
is not reachable then it adds to the replica) and much better error
reporting than ConcurrentUpdateSolrServer. The only downside is lack of
batching. As long as you are adding documents in decent si
Matt:
You might want to look at SolrJ, in particular with the use of CloudSolrServer.
The big benefit here is that it'll route the docs to the correct leader for each
shard rather than relying on the nodes to communicate with each other.
Here's a SolrJ example. NOTE: it used ConcurrentUpdateSolrS
Thanks for the info Daniel. I will go forth and make a better client.
On Oct 29, 2014, at 2:28 AM, Daniel Collins wrote:
> I kind of think this might be "working as designed", but I'll be happy to
> be corrected by others :)
>
> We had a similar issue which we discovered by accident, we had 2
I kind of think this might be "working as designed", but I'll be happy to
be corrected by others :)
We had a similar issue which we discovered by accident, we had 2 or 3
collections spread across some machines, and we accidentally tried to send
an indexing request to a node in teh cloud that didn'
