Thanks guys, this makes sense I guess, from Solr's side.
Perhaps we can have a new Collections API like REDIRECTREPLICA or
something, that will redirect a replica to the new node.
This API can simply do ADDREPLICA on the new node, and DELETEREPLICA of the
node that doesn't exist anymore.
I guess
Yes, it applies to both. Solr wouldn't auto-add replicas in either of those
cases (or any other case) to meet the rf specified at create time.
On Tue, Mar 24, 2015 at 2:22 AM, Shai Erera wrote:
> Thanks Anshum,
>
> About #3, i line with my answer to the previous question, Solr wouldn't
> > auto-
On 3/24/2015 3:22 AM, Shai Erera wrote:
>>> If this is explained somewhere, I'd appreciate if you can give me a
>>> pointer.
I don't think it's explained anywhere, so that's a lack in the
documentation.
One problem with automatic replica addition in response to cluster
problems is that there is n
Thanks Anshum,
About #3, i line with my answer to the previous question, Solr wouldn't
> auto-add a Replica to meet the replication factor when a node goes down.
>
Just to make sure the answer applies to both these cases:
1. There are two replicas on node1 and node2. Solr won't add a replica
Hi Shai,
As of now, all replicas for a collections are created to meet the specified
replication factor at the time of collection creation. There's no way to
defer that until more nodes are up. Your best bet is to have the nodes
already up before you CREATE the collection or create the collection
Hi
I saw that we can define maxShardsPerNode when creating a collection, but I
don't see that I can set something similar for replicas. My scenario is the
following:
- I setup one Solr node
- Create collection with numShards=1 and replicationFactor=2
- Hopefully, one replica is created o
