We do. Indexing is always running. Fix version is 6.3 so can I assume
that the issue is fixed in 6.3? We are running 6.3 right now so or the
fix is not in 6.3 or another issue is causing the full resync.
BR
Arkadi
On 25-11-16 18:23, Pushkar Raste wrote:
Did you index any documents while nod
Did you index any documents while node was being restarted? There was a
issue introduced due to IndexFingerprint comparison. Check SOLR-9310. I am
not sure if fix made it to Solr6.2
On Nov 25, 2016 3:51 AM, "Arkadi Colson" wrote:
> I am using SolrCloud on version 6.2.1. I will upgrade to 6.3.0 n
I am using SolrCloud on version 6.2.1. I will upgrade to 6.3.0 next week.
This is the current config for numVersionBuckets:
${solr.ulog.dir:}
name="numVersionBuckets">${solr.ulog.numVersionBuckets:65536}
Are you saying that I should not use the config below on SolrCloud?
Hold on. Are you using SolrCloud or not? There is a lot of talk here
about masters and slaves, then you say "I always add slaves with the
collection API", collections are a SolrCloud construct.
It sounds like you're mixing the two. You should _not_ configure
master/slave replication parameters wit
This is the code from the master node. Al configs are the same on all
nodes. I always add slaves with the collection API. Is there an other
place to look for this part of the config?
On 24-11-16 12:02, Michael Aleythe, Sternwald wrote:
You need to change this on the master node. The part of t
You need to change this on the master node. The part of the config you pasted
here, looks like it is from the slave node.
-Ursprüngliche Nachricht-
Von: Arkadi Colson [mailto:ark...@smartbit.be]
Gesendet: Donnerstag, 24. November 2016 11:56
An: solr-user@lucene.apache.org
Betreff: Re: AW
