HI Jason, Thanks for this. Without screenshots this is what I get: Site A Last Modified:less than a minute ago Num Docs:5455 Max Doc:5524 Heap Memory Usage:-1 Deleted Docs:69 Version:699 Segment Count:3 Current: Y
Site B Last Modified:3 days ago Num Docs:5454 Max Doc:5523 Heap Memory Usage:-1 Deleted Docs:69 Version:640 Segment Count:3 Current: N I noticed that if I run the command http://hostname:8983/solr/SiteB-Collection/update/?commit=true the index would then be current. I've messed around with auto commit settings in the solrconfig.xml file but had no success. Any help would be greatly appreciated. Thanks, Daniel -----Original Message----- From: Jason Gerlowski <gerlowsk...@gmail.com> Sent: 05 June 2020 12:18 To: solr-user@lucene.apache.org Subject: Re: CDCR behaviour Hi Daniel, Just a heads up that attachments and images are stripped pretty aggressively by the mailing list - none of your images made it through. You might more success linking to the images in Dropbox or some other online storage medium. Best, Jason On Thu, Jun 4, 2020 at 10:55 AM Gell-Holleron, Daniel < daniel.gell-holle...@gb.unisys.com> wrote: > Hi, > > > > Looks for some advice, sent a few questions on CDCR the last couple of > days. > > > > I just want to see if this is expected behavior from Solr or not? > > > > When a document is added to Site A, it is then supposed to replicate > across, however in the statistics page I see the following: > > > > Site A > > > > > Site B > > > > > > When I perform a search on Site B through the Solr admin page, I do > get results (which I find strange). The only way for the numb docs > parameter to be matching is restart Solr, I then get the below: > > > > > > I just want to know whether this behavior is expected or is a bug? My > expectation is that the data will always be current between the two sites. > > > > Thanks, > > Daniel > > >
