My first guess is that you're indexing to the slave nodes. Second guess is that you're re-indexing your entire corpus on the master node.
Third guess is that you're optimizing on the master node (don't do this) What does the slave's log say is the reason? If all the segments on the master have changed, they'll all need to be copied during replication so if that's the case that's entirely normal. And you shouldn't need to commit on the slaves, that should happen as part of replication. Best, Erick On Fri, Jun 15, 2018 at 3:25 AM, Adarsh Hd <hd.ada...@infor.com> wrote: > Hi All, > > Current am using SOLR 5.2.1 on Linux machine. I have cluster of 5 nodes with > master and salve configuration, which gives 5 master nodes and 5slave node. > We have enabled only hard commit on master nodes and both soft & hard commit > on the slave nodes since the search will happen on slave. > Current we are facing a issue which is causing our slave to replicate full > copy from master most of the time , sometimes I get error like unable to > clean old index so trigger full copy I could understand that from couple of > solr links, but there is lot of time where the full copy is triggered just > like with out any warning or any error message could anyone let me know the > possibilities that might trigger the full copy replication so often. > > > Regards > Adarsh
