Hi,
We still use the legacy implementation of solr (not solrcloud), although a
late version (8.3.0)
I've noticed that if replication is disabled on the master, then the index
appears to be removed from a slave.
I've tracked this down to
https://github.com/apache/lucene-solr/blame/master/solr/core/src/java/org/apache/solr/handler/IndexFetcher.java
(line 444) changed with this jira 'SOLR-11293: Fix downgrade in
performance from precommit' in 2017.
It was changed from "if (forceReplication && commit.getGeneration() != 0)
{" to "if (commit.getGeneration() != 0) {" the effect removing the index on
the slave.
Reinstating this flag fixes the issue, but would this be the right
approach? Has anyone else noticed this?
Cheers,
Dan
We still use the legacy implementation of solr (not solrcloud), although a
late version (8.3.0)
I've noticed that if replication is disabled on the master, then the index
appears to be removed from a slave.
I've tracked this down to
https://github.com/apache/lucene-solr/blame/master/solr/core/src/java/org/apache/solr/handler/IndexFetcher.java
(line 444) changed with this jira 'SOLR-11293: Fix downgrade in
performance from precommit' in 2017.
It was changed from "if (forceReplication && commit.getGeneration() != 0)
{" to "if (commit.getGeneration() != 0) {" the effect removing the index on
the slave.
Reinstating this flag fixes the issue, but would this be the right
approach? Has anyone else noticed this?
Cheers,
Dan