On Feb 4, 2008 2:20 PM, Rachel McConnell <[EMAIL PROTECTED]> wrote: > > 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?
Right. Duplicates are removed on a commit(), so if a snapshot is being taken at any other time than right after a commit, those deletes will not have been performed. > I'd have thought that in that case, > the dupe values would stick around until the next update, 20 minutes > later, If you don't call commit() on the master, those dups will still be there. -Yonik
