tlogs on Solr, not ZooKeeper. ZooKeeper is not involved in individual
Solr operations (indexing querying and the like), it just keeps the
state of the nodes
While recovery is happening, updates are still forwarded to the node
that is recovering. They're written to the local tlog then replayed
Thanks Erick for the reply.
When the leader asks the follower to go into recovery status, does it stop
sending future updates to this replica until it becomes fully in sync with
the leader?
Regards
Suresh
On Mon, Jun 5, 2017 at 8:32 PM, Erick Erickson
wrote:
> bq: This means that technically
GW,
Did you mean a separate transaction log on Solr or on Zookeeper?
-suresh
On Tue, Jun 6, 2017 at 5:23 AM, GW wrote:
> I've heard of systems tanking like this on Windows during OS updates.
> Because of this, I run all my updates in attendance even though I'm Linux.
> My Nodes run as VM's, I s
I've heard of systems tanking like this on Windows during OS updates.
Because of this, I run all my updates in attendance even though I'm Linux.
My Nodes run as VM's, I shut down Solr gracefully, snap shot a backup of
the VM, update and run. If things go screwy I can always roll back. To me
it soun
bq: This means that technically the replica nodes should not fall behind and do
not have to go into recovery mode
Well, true if nothing weird happens. By "weird" I mean anything that
interferes with the leader getting anything other than a success code
back from a follower it sends document to.
Hi,
Why and in what scenarios do Solr nodes go into recovery status?
Given that Solr is a CP system it means that the writes for a Document
index are acknowledged only after they are propagated and acknowledged by
all the replicas of the Shard.
This means that technically the replica nodes shoul
