One other question related to this.
I know the change was made for a specific problem that was occurring but has
this caused a similar problem as mine with anyone else?
We're looking to try changing the second 'if' statement to add an extra
conditional to prevent it from performing the
I removed the replicate after startup from our solrconfig.xml file. However
that didn't solve the issue. When I rebuilt the primary, the associated
replicas all went to 0 documents.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
We are currently using the replicate after commit and startup
${replication.enable.master:false}
commit
startup
schema.xml,stopwords.txt
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Hi,
We recently upgraded to SOLR 7.5 in AWS, we had previously been running SOLR
6.5. In our current configuration we have our applications broken into a
single instance primary environment and a multi-instance replica environment
separated behind a load balancer for each environment.
Until
