A pedantic nit... leader/replica is not much like
"old master/slave".
That out of the way, here's what I'd do.
1> use the ADDREPLICA to add a new replica for the shard
_on the same node as the bad one_.
2> Once that had recoverd (green in the admin UI) and you
were confident of
its integrity (you can verify by running queries against this
new replica and the leader with &distrib=false), use
DELETEREPLICA on the "bad" core.
Best,
Erick
On Wed, Jun 1, 2016 at 5:54 AM, Ilan Schwarts <ila...@gmail.com> wrote:
> Hi,
> We have in lab SolrCloud 5.2.1
> 2 Shards, each shard has 2 cores/nodes, replication factor is 1. meaning
> that one node is leader (like old master-slave).
> (upon collection creation numShards=1 rp=1)
>
> Now there is a problem in the lab, shard 1 has 2 cores, but the number of
> docs is different, and when adding a document to one of the cores, it will
> not replicate the data to the other one.
> If i check cluster state.json it appears fine, it writes there are 2 active
> cores and only 1 is set as leader.
>
> What is the recovery method for a scenario like this ? I dont have logs
> anymore and cannot reproduce.
> Is it possible to merge the 2 cores into 1, and then split that core to 2
> cores ?
> Or maybe to enforce sync if possible ?
>
> The other shard, Shard 2 is functioning well, the replication works fine,
> when adding a document to 1 core, it will replicate it to the other.
>
> --
>
>
> -
> Ilan Schwarts
