On 2/4/08, Yonik Seeley <[EMAIL PROTECTED]> wrote: > On Feb 4, 2008 1:48 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote: > > On 2/4/08, Yonik Seeley <[EMAIL PROTECTED]> wrote: > > > On Feb 4, 2008 1:15 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote: > > > > We are using Solr's replication scripts. They are set to run every 20 > > > > minutes, via a cron job on the slave servers. Any further useful info > > > > I can give regarding them? > > > > > > Are you using the postCommit hook in solrconfig.xml to call snapshooter? > > > > No, just the crontab. We have only one master server on which commits > > are made, and the servers on which requests are made run the > > snapshooter periodically. > > If you are running snapshooter asynchronously, this would be the cause. > It's designed to be run from solr (via a postCommit or postOptimize > hook) at specific points where a consistent view of the index is > available.
So our cron job might be running DURING an update, for example, and get duplicate values that way? I'd have thought that in that case, the dupe values would stick around until the next update, 20 minutes later, and we have not observed that to happen. Or do you mean something else? thanks, Rachel
