With those settings, you never commit the documents on the target, thus they are never searchable on the target.
No, I do _not_ recommend you issue a manual commit on the target, that was just a manual test to see if your issue was about commits. I'd just either set openSearcher to true in the <autocommit> section or perhaps set autoSoftCommit to something other than -1, which means "never". Set it to as long as you can stand, soft commits are not as expensive as hard commits, but they aren't free. See: https://lucidworks.com/blog/2013/08/23/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ Best, Erick On Mon, Nov 21, 2016 at 7:11 PM, gayatri.umesh <gayatri.um...@mathworks.com> wrote: > Thank you Erick for pointing out. I missed that!! > > Below are the commit settings in solrconfig.xml in both source and target. > <autoCommit> > <maxTime>${solr.autoCommit.maxTime:15000}</maxTime> > <openSearcher>false</openSearcher> > </autoCommit> > > <autoSoftCommit> > <maxTime>${solr.autoSoftCommit.maxTime:-1}</maxTime> > </autoSoftCommit> > > Is it recommended to issue a commit on the target when indexing the > document, as replication does not autocommit? Or should I enable autocommit > in the target solrconfig? > > Thanks, > Gayatri > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Solr6-CDCR-indexing-doc-to-source-replicates-to-target-doc-not-searchable-in-target-tp4306717p4306816.html > Sent from the Solr - User mailing list archive at Nabble.com.
