Re: Replicationhandler with TLOG replicas

2018-11-10 Thread Shawn Heisey

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 commands)
Is information returned  by Replicationhandler  not applicable to tlog/pull
replicas and is not reliable ?


SolrCloud does not use the replication handler in the same way that 
master/slave replication does.  It "manually" initiates any replication 
that takes place -- the replication handler is not in charge.  You 
cannot be sure that the indexes the replication handler thinks are 
master and slave are in fact the indexes that will be replicated next.  
Just ignore anything that the replication handler tells you.  It may 
have absolutely no bearing on what's happening.


Was indexing happening when you looked, or was it entirely stopped?  If 
indexing is ongoing, you may have seen the difference in the index 
versions in between data being indexed on the leader and the time that 
the replication is initiated.


Thanks,
Shawn



Replicationhandler with TLOG replicas

2018-11-10 Thread Vadim Ivanov
Hello!
I have SolrCloud 7.5 with TLOG replicas.
I have noticed that information about replication state of replicas differs
when received from 
...core/admin/mbeans?stats=true=replication=true=REPLICATION
And 
...core/replication?command=indexversion

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 commands)
Is information returned  by Replicationhandler  not applicable to tlog/pull
replicas and is not reliable ?

-- 
Vadim