On 11/2/2018 3:12 AM, Vadim Ivanov wrote:
It seems to me that issue related with:
- restart solr node
- rebalance leader
- reload collection
- reload core (Core admin is not forbidden but seems obsolete in SolrCloud)
In SolrCloud, CoreAdmin is an expert option. Many of the things that
the Col
" SolrCloud Replication
Failure" branch
-- Vadim
> -Original Message-
> From: Ere Maijala [mailto:ere.maij...@helsinki.fi]
> Sent: Thursday, November 01, 2018 5:21 PM
> To: solr-user@lucene.apache.org
> Subject: Re: TLOG replica stucks
>
> Could it be related to
Could it be related to reloading a collection? I need to do some
testing, but it just occurred to me that reload was done at least once
during the period the cluster had been up.
Regards,
Ere
Ere Maijala kirjoitti 30.10.2018 klo 12.03:
Hi,
We had the same happen with PULL replicas with Solr
Hi,
We had the same happen with PULL replicas with Solr 7.5. Solr was
showing that they all had correct index version, but the changes were
not showing. Unfortunately the solr.log size was too small to catch any
issues, so I've now increased and waiting for it to happen again.
Regards,
Ere
Thanks Erick for you attention!
My comments below, but supposing that the problem resides in zookeeper
I'll collect more information from zk logs and solr logs and be back soon.
> bq. I've noticed that some replicas stop receiving updates from the
> leader without any visible signs from the clus
bq. I've noticed that some replicas stop receiving updates from the
leader without any visible signs from the cluster status.
Hmm, yes, this isn't expected at all. What are you seeing that causes
you to say this? You'd have to be monitoring the log for update
messages to the replicas that aren't l
