/PULL replica.
Thanks.
From: Erick Erickson
Sent: Thursday, December 12, 2019 22:49
To: Hongxu Ma
Subject: Re: A question of solr recovery
If you’re using TLOG/PULL replica types, then only changed segments
are downloaded. That replication pattern has a very diff
On 12/12/2019 8:53 AM, Shawn Heisey wrote:
I do not think the replication handler deals with tlog files at all. The
transaction log capability did not exist when the replication handler
was built.
I may have mixed up your message with a different one. Looking back
over this, I don't see any
On 12/12/2019 3:37 AM, Hongxu Ma wrote:
And I found my "full sync" log:
"IndexFetcher Total time taken for download
(fullCopy=true,bytesDownloaded=178161685180) : 4377 secs (40704063 bytes/sec) to
NIOFSDirectory@..."
A more question:
Form the log, looks it downloaded all segment files (178GB),
database does):
* recovery form local tlog as much as possible
* calculate the latest version
* only download the segment file which contains data > this version
Thanks.
From: Erick Erickson
Sent: Wednesday, December 11, 2019 20:56
To: solr-user@lucene
Updates in this context are individual documents, either new ones
or a new version of an existing document. Long recoveries are
quite unlikely to be replaying a few documents from the tlog.
My bet is that you had to do a “full sync” (there should be messages
to that effect in the Solr log). This m
Hi all
In my cluster, Solr node turned into long time recovery sometimes.
So I want to know more about recovery and have read a good blog:
https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/
It mentioned in the recovery section:
"Replays the documents fro
