.@sematext.com> wrote:
>>>
>>>> Hi Sripradeep,
>>>> Simplified: TLog files are used to replay index updates from the last
>>>> successful hard commit in case of some Solr crashes. It is used on the
>> next
>>>> Solr startup. It does not
dates, otherwise, it would
> >> duplicate the index size.
> >> If you start from these premises, you will understand why it is not
> copied
> >> when adding replicas and why it is not needed and why you cannot use
> TLog
> >> to spin up a new cluster.
otherwise, it would
>> duplicate the index size.
>> If you start from these premises, you will understand why it is not copied
>> when adding replicas and why it is not needed and why you cannot use TLog
>> to spin up a new cluster.
>>
>> HTH,
>> Emir
sed on the next
> Solr startup. It does not contain all updates, otherwise, it would
> duplicate the index size.
> If you start from these premises, you will understand why it is not copied
> when adding replicas and why it is not needed and why you cannot use TLog
> to spin up
will understand why it is not copied when
adding replicas and why it is not needed and why you cannot use TLog to spin up
a new cluster.
HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> On 18 N
replica so adding a
new replica to the already created collection with data/index is not
advisable?
3) Is there a way to make the newly added slave node to replicate the
tlog file as it does for the data/index files from leader?
4) Is it possible to use the Tlog files /index files from an existing
