>
> --
> BR, Vadim
>
>
> > -Original Message-
> > From: Erick Erickson [mailto:erickerick...@gmail.com]
> > Sent: Sunday, November 11, 2018 9:51 PM
> > To: solr-user
> > Subject: Re: Replicationhandler with TLOG replicas
> >
> > Vadim:
${solr.autoCommit.maxTime:6}
false
${solr.autoSoftCommit.maxTime:30}
--
BR, Vadim
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail.com]
> Sent: Sunday, November 11, 2018 9:51 PM
> To: solr-user
> Subject
---
> > From: Vadim Ivanov [mailto:vadim.iva...@spb.ntk-intourist.ru]
> > Sent: Sunday, November 11, 2018 1:09 PM
> > To: solr-user@lucene.apache.org
> > Subject: RE: Replicationhandler with TLOG replicas
> >
> > Thanks, Shawn
> > I have anticipated
o: solr-user@lucene.apache.org
> Subject: RE: Replicationhandler with TLOG replicas
>
> Thanks, Shawn
> I have anticipated the answer about information returned by
> ReplicationHandler.
> What baffled me is that usually on most of replicas indexversion and
> generation
> returne
ase as I have adequate information of
indexversion
and generation returned by mbeans, just curious of that strange behavior.
> -Original Message-
> From: Shawn Heisey [mailto:apa...@elyograg.org]
> Sent: Saturday, November 10, 2018 6:46 PM
> To: solr-user@lucene.apache.org
> Subject: Re
On 11/10/2018 8:05 AM, Vadim Ivanov wrote:
Seems, the latter gets some wrong information as indexversion and generation
is far behind then leader.
But core index seems up to date and healthy.
Why such things could happen on some replicas? (Most of the replicas retuned
the same information by both
