Hi Vadim,
There is no commit on TLOG/PULL follower replicas, only on the leader.
Followers fetch the segments and **reload the core** every 150 seconds (if
there were new segments, I suppose). Yeah, followers don't pay the CPU
price of indexing, but there are still cache invalidation, autowarming
If hard commit max time is 300 sec then commit happens every 300 sec on tlog
leader. And new segments pop up on the leader every 300 sec, during indexing.
Polling interval on other replicas 150 sec, but not every poll attempt they
fetch new segment from the leader, afaiu. Erick, do you mean th
Hi
I have read here [1] and here [2] that it is possible to highlight only
parent documents in block join queries. But I didn't succeed yet:
So here is my nested document example:
[
{
"id": "2",
"type_s": "parent",
"content_txt": ["apache"],
"_childDocuments_":
Not quite, 60. The polling interval is half the commit interval
This has always bothered me a little bit, I wonder at the utility of a
config param. We already have old-style replication with a
configurable polling interval. Under very heavy indexing loads, it
seems to me that either the t
Thanks Mikhail
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Thanks, Edward, for clues.
What bothers me is newSearcher start, warming, cache clear... all that CPU
consuming stuff in my heavy-indexing scenario.
With NRT I had autoSoftCommit: 30.
So I had new Searcher no more than every 5 min on every replica.
To have more or less the same effect wit
