Hey,
I am encountering an issue which looks a lot like
https://issues.apache.org/jira/browse/SOLR-6763.
However, it seems like the fix for that does not address the entire problem.
That fix will only work if we hit the zkClient.getChildren() call before the
reconnect logic has finished reconne
make sure that the node with data
>becomes the leader. So just keep the cluster running while adding a new
>node.
>
>Also, stop relying on core discovery for setting up a node. At some point
>we will stop supporting this feature. Use the collection API to add new
>replicas.
>
Hi,
I am seeing some unexpected behavior when adding a new machine to my cluster. I
am running 4.10.3.
My setup has multiple collections, each collection has a single shard. I am
using core auto discovery on the hosts (my deployment mechanism ensures that
the directory structure is created and
Hi,
I have a SolrCloud setup, running 4.10.3. The setup consists of several cores,
each with a single shard and initially each shard has a single replica (so,
basically, one machine). I am using core discovery, and my deployment tools
create an empty core on newly provisioned machines.
The sce
Hi,
I'm seeing some odd behavior that I am hoping someone could explain to me.
The configuration I'm using to repro the issue, has a ZK cluster and a single
Solr instance. The instance has 10 Cores, and none of the cores are sharded.
The initial startup is fine, the Solr instance comes up and w
