This isn't a problem. The index on the master node in master/slave (searching) is the last time the _master_ opened a searcher whereas (replicable) is the last hard commit. These are identical if you to hard commits with openSearcher=true.
They are different if you have openSearcher=false for your hard commits and then do a soft commit. For SolrCloud these are irrelevant distinctions. For a lot about the difference between commits, see: https://lucidworks.com/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ Best, Erick On Mon, Jul 31, 2017 at 10:33 AM, Nawab Zada Asad Iqbal <khi...@gmail.com> wrote: > Hi, > > From the solr console, I see 'master (searching)' and 'master > (replicable)' fields on `host/solr/#/core_1/replication` page and wondering > how does it impact me given that I don't have any replicas. > > If I don't have any replicas, does it make any impact on performance by > enabling or disabling replication? > > Also, when i am indexing new documents, I see `master (searching)` size > growing even when I disable the replication from this UI. What does it > imply? > > > Regards > Nawab
