Thanks Erick ! Great details as always :)
> On Mar 13, 2019, at 8:48 AM, Erick Erickson wrote:
>
> Wei:
>
> Right. You should count on the _entire_ index being replicated from the
> leader, but only after the optimize is done. Pre 7.5, this would be a single
> segment, 7.5+ it would be a bunc
Wei:
Right. You should count on the _entire_ index being replicated from the leader,
but only after the optimize is done. Pre 7.5, this would be a single segment,
7.5+ it would be a bunch of 5G flies unless you specified that the optimize
create some number of segments.
But unless you
1> have
Hi Erick
A related question:
Is optimize then ill advised for bulk indexer post solr 7.5 ?
>> Especially in a situation where an index is being modified over many days ?
Thanks
Aroop
> On Mar 12, 2019, at 9:30 PM, Wei wrote:
>
> Thanks Erick, it's very helpful. So for bulking indexing in a
Thanks Erick, it's very helpful. So for bulking indexing in a Tlog or
Tlog/Pull cloud, when we optimize at the end of updates, segments on the
leader replica will change rapidly and the follower replicas will be
continuously pulling from the leader, effectively downloading the whole
index. Is th
do _not_ turn of hard commits, even when bulk indexing. Set the OpenSeacher to
false in your config. This is for two reasons:
1> the only time the transaction log is rolled over is when a hard commit
happens. If you turn off commits it’ll grow to a very large size.
2> If, for any reason, the node
A side question, for heavy bulk indexing, what's the recommended setting
for auto commit? As there is no query needed during the bulking indexing
process, I have auto soft commit disabled. Is there any side effect if I
also disable auto commit?
On Sun, Mar 10, 2019 at 10:22 PM Wei wrote:
> Thank
Thanks Erick.
1> TLOG replicas shouldn’t optimize on the follower. They should optimize
on the leader then replicate the entire index to the follower.
Does that mean the follower will ignore the optimize request? Or shall I
send the optimize request only to one of the leaders?
2> As of Solr 7.5,
This is very odd for at least two reasons:
1> TLOG replicas shouldn’t optimize on the follower. They should optimize on
the leader then replicate the entire index to the follower.
2> As of Solr 7.5, optimize should not optimize to a single segment _unless_
that segment is < 5G. See LUCENE-7976.
Hi,
RecentIy I encountered a strange issue with optimize in Solr 7.6. The cloud
is created with 4 shards with 2 Tlog replicas per shard. After batch index
update I issue an optimize command to a randomly picked replica in the
cloud. After a while when I check, all the non-leader Tlog replicas
fi
