Unfortunately nothing of the both works well for me.
1. Restarting all nodes leads to described situation on some shards.
Even if no alternatives for the shard it does not gain the leader
(all other replicas on down nodes). I suppose it waits for somw timeout.
But what timeout and can it be altered
There are a couple of options:
1> stop all your nodes. Start them one at a time and wait for "leader
election" to occur. This can take several minutes, but eventually the
replicas on that machine will become the leader. Then start the other
nodes, again one at a time waiting for them to recover fu
For latitude and longitude data, I recommend "lat,lon" and never use "x
y". Perhaps the latter should be an error when geo=true (and inverse when
false) but it isn't. Yes the documentation could be better!
On Fri, Dec 21, 2018 at 4:31 AM Peter Lancaster <
peter.lancas...@findmypast.com> wrote:
Hi!
After restart of nodes I have situation when no leader on shard can be
elected
Shard rpk51_222_306 resides on 3 nodes (solr00, solr06, solr09) with
corresponding replica names
(rpk51_222_306_00, rpk51_222_306_06, rpk51_222_306_09)
Logs looks like this
PeerSync: core=rpk51_222_306_00 url=http:
