What is the intended use case and behavior of disablereplication?

My expectation was that it would be to cause the master to not respond to
 slave requests.

Working with a master/slave Solr 7.1 setup; slave is set up to poll every
60s. I would prefer to remain on M/S for immediate future, while we are
resolving instability in the ingestion pipeline external to Solr, which
causes bad data to be ingested.

Testing failure scenarios related to data corruption, disabled replication
at the master:
curl http://
$SOLR_NODE/solr/$COLLECTION/replication?command=disablereplication

But did not disable polling at the slaves.

2018-02-02 14:05:13.775 INFO  (indexFetcher-16-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Master's generation: 0
2018-02-02 14:05:13.776 INFO  (indexFetcher-16-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Master's version: 0
2018-02-02 14:05:13.776 INFO  (indexFetcher-16-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Slave's generation: 12254
2018-02-02 14:05:13.776 INFO  (indexFetcher-16-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Slave's version: 1517493295318
2018-02-02 14:05:13.776 INFO  (indexFetcher-16-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher New index in Master. Deleting mine...

And the slave did indeed delete all its documents.
Master's generation at the time was also 12254.

Re-enabled replication at the master, slave caught back up again :
Normal behavior when master and slave are in sync, the slave polls:
2018-02-02 16:08:31.489 INFO  (indexFetcher-24-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Master's generation: 12258
2018-02-02 16:08:31.489 INFO  (indexFetcher-24-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Master's version: 1517595712709
2018-02-02 16:08:31.489 INFO  (indexFetcher-24-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Slave's generation: 12258
2018-02-02 16:08:31.489 INFO  (indexFetcher-24-thread-1) [   x:collection1]
o.a.s.h.IndexFetcher Slave's version: 1517595712709

Things that delete the index are big glaring problems, but I'm not clear if
this is a Solr bug or user error.

Liz

Reply via email to